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>
René Scharfe committed
Nov 27, 2013 at 01:28 UTC
eaa6c987e68c78a2d537480c5b06c42177f9c286
1 file changed
+9
-2
Documentation/SubmittingPatches
+9
-2
@@ -126,8 +126,15 @@ People on the Git mailing list need to be able to read and
126
comment on the changes you are submitting. It is important for
127
a developer to be able to "quote" your changes, using standard
128
e-mail tools, so that they may comment on specific portions of
129
-your code. For this reason, all patches should be submitted
130
-"inline". If your log message (including your name on the
129
+your code. For this reason, each patch should be submitted
130
+"inline" in a separate message.
131
+
132
+Multiple related patches should be grouped into their own e-mail
133
+thread to help readers find all parts of the series. To that end,
134
+send them as replies to either an additional "cover letter" message
135
+(see below), the first patch, or the respective preceding patch.
136
+
137
+If your log message (including your name on the
138
Signed-off-by line) is not writable in ASCII, make sure that
139
you send off a message in the correct encoding.
140