doc: clarify practices for submitting updated patch versions
The `SubmittingPatches` documentation briefly mentions that related patches should be grouped together in their own e-mail thread. Expand on this to explicitly state that updated versions of a patch series should also follow this. Also provide add a link to existing documentation from `MyFirstContribution` that provides detailed instructions on how to do this via `git-send-email(1)`. Signed-off-by: Justin Tobler <jltobler@gmail.com> Signed-off-by: Junio C Hamano <gitster@pobox.com>
Justin Tobler committed
Apr 25, 2024 at 16:34 UTC
4cf6e7bf5e3e81bb7bda7cc22eb29961743b81b9
1 file changed
+6
-4
Documentation/SubmittingPatches
+6
-4
@@ -415,10 +415,12 @@ e-mail tools, so that they may comment on specific portions of
415
your code. For this reason, each patch should be submitted
416
"inline" in a separate message.
417
418
-Multiple related patches should be grouped into their own e-mail
419
-thread to help readers find all parts of the series. To that end,
420
-send them as replies to either an additional "cover letter" message
421
-(see below), the first patch, or the respective preceding patch.
418
+All subsequent versions of a patch series and other related patches should be
419
+grouped into their own e-mail thread to help readers find all parts of the
420
+series. To that end, send them as replies to either an additional "cover
421
+letter" message (see below), the first patch, or the respective preceding patch.
422
+Here is a link:MyFirstContribution.html#v2-git-send-email[step-by-step guide] on
423
+how to submit updated versions of a patch series.
424
425
If your log message (including your name on the
426
`Signed-off-by` trailer) is not writable in ASCII, make sure that