SubmittingPatches: clarify the purpose of the final resend
Signed-off-by: Junio C Hamano <gitster@pobox.com>
Junio C Hamano committed
Oct 9, 2020 at 11:56 UTC
d95b192efda2c437d7a44f15db6d9b9f6ac1b5f9
1 file changed
+5
-3
Documentation/SubmittingPatches
+5
-3
@@ -290,12 +290,14 @@ identify them), to solicit comments and reviews.
290
:git-ml: footnote:[The mailing list: git@vger.kernel.org]
291
292
After the list reached a consensus that it is a good idea to apply the
293
-patch, re-send it with "To:" set to the maintainer{current-maintainer} and "cc:" the
294
-list{git-ml} for inclusion.
293
+patch, re-send it with "To:" set to the maintainer{current-maintainer}
294
+and "cc:" the list{git-ml} for inclusion. This is especially relevant
295
+when the maintainer did not heavily participate in the discussion and
296
+instead left the review to trusted others.
297
298
Do not forget to add trailers such as `Acked-by:`, `Reviewed-by:` and
299
`Tested-by:` lines as necessary to credit people who helped your
298
-patch.
300
+patch, and "cc:" them when sending such a final version for inclusion.
301
302
[[sign-off]]
303
=== Certify your work by adding your "Signed-off-by: " line