Skip to content

Commit 104cf14

Browse files
committed
Merge branch 'jt/doc-submitting-rerolled-series' into maint-2.45
Developer doc update. * jt/doc-submitting-rerolled-series: doc: clarify practices for submitting updated patch versions
2 parents 2e416ef + 4cf6e7b commit 104cf14

File tree

1 file changed

+6
-4
lines changed

1 file changed

+6
-4
lines changed

Documentation/SubmittingPatches

Lines changed: 6 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -415,10 +415,12 @@ e-mail tools, so that they may comment on specific portions of
415415
your code. For this reason, each patch should be submitted
416416
"inline" in a separate message.
417417

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.
422424

423425
If your log message (including your name on the
424426
`Signed-off-by` trailer) is not writable in ASCII, make sure that

0 commit comments

Comments
 (0)