undef/git-commit-vandalism
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Merge branch 'rs/doc-submitting-patches'

Browse Source 
* rs/doc-submitting-patches:
  SubmittingPatches: document how to handle multiple patches
This commit is contained in:
Junio C Hamano 2013-12-12 14:18:29 -08:00
commit fca26a3430
1 changed files with 9 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

11
Documentation/SubmittingPatches
View File

@ -139,8 +139,15 @@ People on the Git mailing list need to be able to read and
comment on the changes you are submitting. It is important for comment on the changes you are submitting. It is important for
a developer to be able to "quote" your changes, using standard a developer to be able to "quote" your changes, using standard
e-mail tools, so that they may comment on specific portions of e-mail tools, so that they may comment on specific portions of
your code. For this reason, all patches should be submitted your code. For this reason, each patch should be submitted
"inline". If your log message (including your name on the "inline" in a separate message.
Multiple related patches should be grouped into their own e-mail
thread to help readers find all parts of the series. To that end,
send them as replies to either an additional "cover letter" message
(see below), the first patch, or the respective preceding patch.
If your log message (including your name on the
Signed-off-by line) is not writable in ASCII, make sure that Signed-off-by line) is not writable in ASCII, make sure that
you send off a message in the correct encoding. you send off a message in the correct encoding.