diff options
| author | Junio C Hamano <gitster@pobox.com> | 2024-05-31 15:28:20 -0700 |
|---|---|---|
| committer | Junio C Hamano <gitster@pobox.com> | 2024-05-31 15:28:21 -0700 |
| commit | 104cf1422c69ddfed24a50e220d61bca63567be8 (patch) | |
| tree | f33ff30fe7e50304b689f8730ad5269993b69d26 | |
| parent | 2e416ef0668b707aa59ab48df305093e73565645 (diff) | |
| parent | 4cf6e7bf5e3e81bb7bda7cc22eb29961743b81b9 (diff) | |
| download | git-104cf1422c69ddfed24a50e220d61bca63567be8.tar.gz | |
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
| -rw-r--r-- | Documentation/SubmittingPatches | 10 |
1 files changed, 6 insertions, 4 deletions
diff --git a/Documentation/SubmittingPatches b/Documentation/SubmittingPatches index c404fadf0e..625bdd0bb6 100644 --- a/Documentation/SubmittingPatches +++ b/Documentation/SubmittingPatches @@ -415,10 +415,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 |