aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorJunio C Hamano <gitster@pobox.com>2024-05-02 11:21:45 -0700
committerJunio C Hamano <gitster@pobox.com>2024-05-02 11:21:45 -0700
commitbf73ddaf7cf364d3d788dc45406555411d5d433f (patch)
treef920216d9f27f53745dbae32c9ddee3828989b5c
parenta660a398eb8dede368b6013b79a5d736ac6b9d17 (diff)
parent4cf6e7bf5e3e81bb7bda7cc22eb29961743b81b9 (diff)
downloadgit-bf73ddaf7cf364d3d788dc45406555411d5d433f.tar.gz
Merge branch 'jt/doc-submitting-rerolled-series' into jch
Notice: this object is not reachable from any branch.
Developer doc update. * jt/doc-submitting-rerolled-series: doc: clarify practices for submitting updated patch versions
Notice: this object is not reachable from any branch.
-rw-r--r--Documentation/SubmittingPatches10
1 files changed, 6 insertions, 4 deletions
diff --git a/Documentation/SubmittingPatches b/Documentation/SubmittingPatches
index e70a9a0f35..384893be1c 100644
--- a/Documentation/SubmittingPatches
+++ b/Documentation/SubmittingPatches
@@ -455,10 +455,12 @@ e-mail tools, so that they may comment on specific portions of
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.
+All subsequent versions of a patch series and other 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.
+Here is a link:MyFirstContribution.html#v2-git-send-email[step-by-step guide] on
+how to submit updated versions of a patch series.
If your log message (including your name on the
`Signed-off-by` trailer) is not writable in ASCII, make sure that