diff options
| author | Junio C Hamano <gitster@pobox.com> | 2024-05-01 14:02:50 -0700 |
|---|---|---|
| committer | Junio C Hamano <gitster@pobox.com> | 2024-05-01 14:02:51 -0700 |
| commit | 1c5865f11cfe913f3c0c17c205971249d0c3e0fc (patch) | |
| tree | f920216d9f27f53745dbae32c9ddee3828989b5c | |
| parent | 7020ecebe75072b4b408fbbae31c298e9208c21f (diff) | |
| parent | 4cf6e7bf5e3e81bb7bda7cc22eb29961743b81b9 (diff) | |
| download | git-1c5865f11cfe913f3c0c17c205971249d0c3e0fc.tar.gz | |
Merge branch 'jt/doc-submitting-rerolled-series' into next
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 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 |