From: Matthieu Moy <Matthieu.Moy@grenoble-inp.fr>
To: Stefan Beller <sbeller@google.com>
Cc: Junio C Hamano <gitster@pobox.com>,
Lars Schneider <larsxschneider@gmail.com>,
"git\@vger.kernel.org" <git@vger.kernel.org>,
Michael Haggerty <mhagger@alum.mit.edu>
Subject: Re: [PATCH v1] Documentation: add setup instructions for Travis CI
Date: Thu, 14 Apr 2016 11:14:07 +0200 [thread overview]
Message-ID: <vpqmvowwo0w.fsf@anie.imag.fr> (raw)
In-Reply-To: <CAGZ79kYBK-MNYZRo+LsBqng47usGPQTyBe01W2SrKDrs3435sQ@mail.gmail.com> (Stefan Beller's message of "Wed, 13 Apr 2016 10:56:30 -0700")
Stefan Beller <sbeller@google.com> writes:
> On Wed, Apr 13, 2016 at 10:39 AM, Junio C Hamano <gitster@pobox.com> wrote:
>
>> here, create a "GitHub-Travis CI hints" section just before "MUA
>> specific hints" section,
>
> Somebody (I think it was you, Lars?) at GitMerge suggested to break
> up the SubmittingPatches document into more than one, i.e.
> the MUA hints and the Github-Travis hints could become their own documents,
> and the SubmittingPatches could just contain the bare essentials.
I didn't see it on-list, but there's a PR doing that here:
https://github.com/git/git/pull/223
--
Matthieu Moy
http://www-verimag.imag.fr/~moy/
next prev parent reply other threads:[~2016-04-14 9:14 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-13 5:49 [PATCH v1] Documentation: add setup instructions for Travis CI larsxschneider
2016-04-13 17:39 ` Junio C Hamano
2016-04-13 17:56 ` Stefan Beller
2016-04-14 9:14 ` Matthieu Moy [this message]
2016-04-14 17:45 ` Junio C Hamano
2016-04-16 15:29 ` Lars Schneider
2016-05-02 8:12 ` [PATCH v2] " larsxschneider
2016-05-02 8:48 ` Matthieu Moy
2016-05-02 17:21 ` Junio C Hamano
2016-05-03 8:09 ` Lars Schneider
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=vpqmvowwo0w.fsf@anie.imag.fr \
--to=matthieu.moy@grenoble-inp.fr \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=larsxschneider@gmail.com \
--cc=mhagger@alum.mit.edu \
--cc=sbeller@google.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.