diff options
| author |  Junio C Hamano <gitster@pobox.com> | 2013-12-17 11:38:23 -0800 |
|---|---|---|
| committer | Junio C Hamano <gitster@pobox.com> | 2013-12-17 11:38:23 -0800 |
| commit | 59f3e3f1e2b600f122e011b3d90309736799e25d (patch) | |
| tree | 920df6b5dc67df6f784450b0a2733c2f5c83e974 /Documentation | |
| parent | Merge branch 'tr/doc-git-cherry' into maint (diff) | |
| parent | SubmittingPatches: document how to handle multiple patches (diff) | |
| download | tgif-59f3e3f1e2b600f122e011b3d90309736799e25d.tar.xz | |
Merge branch 'rs/doc-submitting-patches' into maint
* rs/doc-submitting-patches:
SubmittingPatches: document how to handle multiple patches
Diffstat (limited to 'Documentation')
| -rw-r--r-- | Documentation/SubmittingPatches | 11 |
1 files changed, 9 insertions, 2 deletions
diff --git a/Documentation/SubmittingPatches b/Documentation/SubmittingPatches index 705557689d..e6d46edbe7 100644 --- a/Documentation/SubmittingPatches +++ b/Documentation/SubmittingPatches @@ -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 a developer to be able to "quote" your changes, using standard e-mail tools, so that they may comment on specific portions of -your code. For this reason, all patches should be submitted -"inline". If your log message (including your name on the +your code. For this reason, each patch should be submitted +"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 you send off a message in the correct encoding. |