From: Junio C Hamano <gitster@pobox•com>
To: Roberto Tyley <roberto.tyley@gmail•com>
Cc: Jeff King <peff@peff•net>,
Matthieu Moy <Matthieu.Moy@grenoble-inp•fr>,
Luke Diamand <luke@diamand•org>,
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: Sat, 03 Oct 2015 18:37:26 -0700 [thread overview]
Message-ID: <xmqq612n2z3d.fsf@gitster.mtv.corp.google.com> (raw)
In-Reply-To: <CAPc5daXkn=C-D5RQCw2w+JrHn7XZA6X-P4F-PugRe-S4Z2RO0g@mail.gmail.com> (Junio C. Hamano's message of "Sat, 3 Oct 2015 18:27:06 -0700")
Junio C Hamano <gitster@pobox•com> writes:
> On Sat, Oct 3, 2015 at 3:23 PM, Roberto Tyley <roberto.tyley@gmail•com> wrote:
>>
>> Given this, enabling Travis CI for git/git seems pretty low risk,
>> are there any strong objections to it happening?
>
> I still don't see a reason why git/git needs to be the one that is
> used, when somebody
> so interested (and I seem to see very many of them in the thread) can
> sacrifice his or
> her own fork and enable it him or herself.
To state it a bit differently.
If somebody says "I've been maintaining a clone of git/git with
Travis webhooks enabled and as the result caught this many glitches
during the past two months without any ill side effect. Here are
the patches to fix them, and by the way, the first patch in this
series is not a fix but the configuration to tell Travis how to run
tests so that other people can enable it on _their_ own fork before
they send their own series to the mailing list." in the cover letter
of a patch series, I would appreciate such a series greatly and
would not mind carrying one extra yml file in the tree at all.
But that is not what I am seeing in this thread at all. I am tired
of hearing people telling others to help them by doing more without
doing the grunt work themselves.
next prev parent reply other threads:[~2015-10-04 1:37 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
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 [this message]
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=xmqq612n2z3d.fsf@gitster.mtv.corp.google.com \
--to=gitster@pobox$(echo .)com \
--cc=Matthieu.Moy@grenoble-inp$(echo .)fr \
--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 \
--cc=peff@peff$(echo .)net \
--cc=roberto.tyley@gmail$(echo .)com \
/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