summaryrefslogtreecommitdiff
path: root/Documentation
diff options
context:
space:
mode:
authorLibravatar René Scharfe <l.s.r@web.de>2013-11-27 01:28:39 +0100
committerLibravatar Junio C Hamano <gitster@pobox.com>2013-11-27 11:05:58 -0800
commiteaa6c987e68c78a2d537480c5b06c42177f9c286 (patch)
treed9cecf600f6012d9136c772851b3391e7be453d4 /Documentation
parentMerge branch 'maint-1.8.2' into maint-1.8.3 (diff)
downloadtgif-eaa6c987e68c78a2d537480c5b06c42177f9c286.tar.xz
SubmittingPatches: document how to handle multiple patches
Signed-off-by: Rene Scharfe <l.s.r@web.de> Signed-off-by: Junio C Hamano <gitster@pobox.com>
Diffstat (limited to 'Documentation')
-rw-r--r--Documentation/SubmittingPatches11
1 files changed, 9 insertions, 2 deletions
diff --git a/Documentation/SubmittingPatches b/Documentation/SubmittingPatches
index d0a4733e45..9d230b3eb2 100644
--- a/Documentation/SubmittingPatches
+++ b/Documentation/SubmittingPatches
@@ -126,8 +126,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.