From: Junio C Hamano Date: Mon, 2 Nov 2020 21:17:47 +0000 (-0800) Subject: Merge branch 'jc/doc-final-resend' X-Git-Tag: v2.30.0-rc0~117 X-Git-Url: http://git.ipfire.org/?a=commitdiff_plain;h=ea9611573ba441359b43c3ddf67fa8ecbefd9166;p=thirdparty%2Fgit.git Merge branch 'jc/doc-final-resend' Update developer doc. * jc/doc-final-resend: SubmittingPatches: clarify the purpose of the final resend --- ea9611573ba441359b43c3ddf67fa8ecbefd9166 diff --cc Documentation/SubmittingPatches index 3bf2147787,87089654ae..d12094bac5 --- a/Documentation/SubmittingPatches +++ b/Documentation/SubmittingPatches @@@ -295,17 -297,20 +297,17 @@@ instead left the review to trusted othe Do not forget to add trailers such as `Acked-by:`, `Reviewed-by:` and `Tested-by:` lines as necessary to credit people who helped your - patch. + patch, and "cc:" them when sending such a final version for inclusion. [[sign-off]] -=== Certify your work by adding your "Signed-off-by: " line +=== Certify your work by adding your `Signed-off-by` trailer -To improve tracking of who did what, we've borrowed the -"sign-off" procedure from the Linux kernel project on patches -that are being emailed around. Although core Git is a lot -smaller project it is a good discipline to follow it. +To improve tracking of who did what, we ask you to certify that you +wrote the patch or have the right to pass it on under the same license +as ours, by "signing off" your patch. Without sign-off, we cannot +accept your patches. -The sign-off is a simple line at the end of the explanation for -the patch, which certifies that you wrote it or otherwise have -the right to pass it on as an open-source patch. The rules are -pretty simple: if you can certify the below D-C-O: +If you can certify the below D-C-O: [[dco]] .Developer's Certificate of Origin 1.1