Re: [PATCH v1] Documentation: add setup instructions for Travis CI

Matthieu Moy [off-list ref] writes:

Stefan Beller [off-list ref] writes:

quoted

On Wed, Apr 13, 2016 at 10:39 AM, Junio C Hamano [off-list ref] wrote:

quoted

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.