From: Junio C Hamano <gitster@pobox.com>
To: Matthieu Moy <Matthieu.Moy@grenoble-inp.fr>,
Roberto Tyley <roberto.tyley@gmail.com>
Cc: Stefan Beller <sbeller@google.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 10:45:26 -0700 [thread overview]
Message-ID: <xmqqr3e8gk3t.fsf@gitster.mtv.corp.google.com> (raw)
In-Reply-To: <vpqmvowwo0w.fsf@anie.imag.fr> (Matthieu Moy's message of "Thu, 14 Apr 2016 11:14:07 +0200")
Matthieu Moy <Matthieu.Moy@grenoble-inp.fr> writes:
> 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
I guess submitGit did not work well there ;-)?
To save one round-trip, I do not think it is unreasonable to treat
submitGit as the first-class MUA that sits next to other recommended
ways to send the patches to the list. It is a rough equivalent to
"format-patch and then send-email". As long as what appears on list
is the authoritative and final form of contribution, those on the
receiving end should not (and would not) care how the patch e-mail
was prepared and sent.
next prev parent reply other threads:[~2016-04-14 17:45 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
2016-04-14 17:45 ` Junio C Hamano [this message]
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=xmqqr3e8gk3t.fsf@gitster.mtv.corp.google.com \
--to=gitster@pobox.com \
--cc=Matthieu.Moy@grenoble-inp.fr \
--cc=git@vger.kernel.org \
--cc=larsxschneider@gmail.com \
--cc=mhagger@alum.mit.edu \
--cc=roberto.tyley@gmail.com \
--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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).