From: Junio C Hamano <gitster@pobox•com>
To: Luke Diamand <luke@diamand•org>
Cc: Johannes Schindelin <johannes.schindelin@gmx•de>,
Dennis Kaarsemaker <dennis@kaarsemaker•net>,
Lars Schneider <larsxschneider@gmail•com>,
Git Users <git@vger•kernel.org>
Subject: Re: [RFC/PATCH v1] Add Travis CI support
Date: Fri, 25 Sep 2015 10:41:35 -0700 [thread overview]
Message-ID: <xmqqsi624cs0.fsf@gitster.mtv.corp.google.com> (raw)
In-Reply-To: <CAE5ih7_f8qy9WvmgRUR6-qFwB4WFhZ6Qr5iOpE0YxqJH8AsZyw@mail.gmail.com> (Luke Diamand's message of "Fri, 25 Sep 2015 09:05:37 +0100")
Luke Diamand <luke@diamand•org> writes:
> From past experience, if it's configured to email people when things
> break, sooner or later it will email the wrong people, probably once
> every few seconds over a weekend.
>
> Automated testing is a Good Thing, but it's still software, so needs
> maintenance or it will break.
That does sound like a valid concern (thanks for education---we
should all learn from others' past experience). Unless it is just a
"set up and forget" thing, I do not think I'd want to be in charge
of it.
Thanks.
next prev parent reply other threads:[~2015-09-25 17:41 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-24 21:43 [RFC/PATCH v1] Add Travis CI support larsxschneider
2015-09-24 21:43 ` larsxschneider
2015-09-25 0:41 ` Junio C Hamano
2015-09-25 3:14 ` Dennis Kaarsemaker
2015-09-25 7:27 ` Johannes Schindelin
2015-09-25 8:05 ` Luke Diamand
2015-09-25 17:41 ` Junio C Hamano [this message]
2015-09-26 16:40 ` Lars Schneider
2015-09-27 12:11 ` Matthieu Moy
2015-09-28 17:21 ` Stefan Beller
2015-09-28 17:37 ` Matthieu Moy
2015-09-28 18:47 ` Junio C Hamano
2015-09-28 19:07 ` Matthieu Moy
2015-10-03 22:23 ` Roberto Tyley
2015-10-04 1:27 ` Junio C Hamano
2015-10-04 1:37 ` Junio C Hamano
2015-10-04 8:13 ` Dennis Kaarsemaker
2015-10-04 12:51 ` Johannes Schindelin
2015-10-04 7:59 ` Matthieu Moy
2015-10-04 17:46 ` Junio C Hamano
2015-10-04 18:06 ` Dennis Kaarsemaker
2015-10-05 6:54 ` Matthieu Moy
2015-10-05 16:51 ` Junio C Hamano
2015-10-12 8:03 ` Sebastian Schuberth
2015-10-04 17:59 ` Junio C Hamano
2015-10-04 3:34 ` Jeff King
2015-10-02 16:40 ` Sebastian Schuberth
2015-09-25 16:26 ` Jeff King
2015-09-25 18:29 ` Junio C Hamano
2015-09-25 18:52 ` Jeff King
2015-09-26 21:54 ` Shawn Pearce
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=xmqqsi624cs0.fsf@gitster.mtv.corp.google.com \
--to=gitster@pobox$(echo .)com \
--cc=dennis@kaarsemaker$(echo .)net \
--cc=git@vger$(echo .)kernel.org \
--cc=johannes.schindelin@gmx$(echo .)de \
--cc=larsxschneider@gmail$(echo .)com \
--cc=luke@diamand$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox