Re: [PATCH 2/2] Add submitGit patch-submission information

2016-04-14 Thread Jeff King
On Thu, Apr 14, 2016 at 03:27:18PM -0700, Junio C Hamano wrote: > > + - Create a pull request on https://github.com/git/git and > > +use https://submitgit.herokuapp.com/ to send it as a patch series > > +to the mailing list. Note that the PR is just the place where your > > +patch is

Re: [PATCH 2/2] Add submitGit patch-submission information

2016-04-14 Thread Junio C Hamano
Junio C Hamano writes: >> +Because of these factors, it's recommended that you use one of these >> +specific methods to generate and send your patchs: > > Perhaps: > > It's recommended ... your patches, unless you already know how > to correctly send your patches as plain-text e-mails. >

Re: [PATCH 2/2] Add submitGit patch-submission information

2016-04-14 Thread Junio C Hamano
Roberto Tyley writes: > +(3) Generate and send your patch to the Git mailing list > > People on the Git mailing list need to be able to read and > comment on the changes you are submitting. It is important for > a developer to be able to "quote" your changes, using standard > e-mail tools,

[PATCH 2/2] Add submitGit patch-submission information

2016-04-14 Thread Roberto Tyley
Most of the guidance on how to use submitGit will stay with the tool itself, so the edits here are mostly to make the choice clear to users. Because generation of patches is quite different for MUA-users and submitGit users, I've merged section 3 and 4 together: section 3 - 'Generate your patch u