Skip to content

Commit 34f34d6

Browse files
committed
Merge branch 'jt/doc-submitting-rerolled-series'
Developer doc update. * jt/doc-submitting-rerolled-series: doc: clarify practices for submitting updated patch versions
2 parents 2c34e4e + 4cf6e7b commit 34f34d6

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
@@ -455,10 +455,12 @@ e-mail tools, so that they may comment on specific portions of
455455
your code. For this reason, each patch should be submitted
456456
"inline" in a separate message.
457457

458-
Multiple related patches should be grouped into their own e-mail
459-
thread to help readers find all parts of the series. To that end,
460-
send them as replies to either an additional "cover letter" message
461-
(see below), the first patch, or the respective preceding patch.
458+
All subsequent versions of a patch series and other related patches should be
459+
grouped into their own e-mail thread to help readers find all parts of the
460+
series. To that end, send them as replies to either an additional "cover
461+
letter" message (see below), the first patch, or the respective preceding patch.
462+
Here is a link:MyFirstContribution.html#v2-git-send-email[step-by-step guide] on
463+
how to submit updated versions of a patch series.
462464

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

0 commit comments

Comments
 (0)