SubmittingPatches: dedupe discussion of security patches
Signed-off-by: Linus Arver <linusa@google.com> Signed-off-by: Junio C Hamano <gitster@pobox.com>
Linus Arver committed
Apr 18, 2024 at 21:52 UTC
01ea2b2836d8caa8ff08f81d4d3dfb5c0264b629
1 file changed
+4
-11
Documentation/SubmittingPatches
+4
-11
@@ -399,12 +399,11 @@ letter.
399
400
==== Choosing your reviewers
401
402
-:security-ml-ref: footnoteref:[security-ml]
402
+:security-ml: footnoteref:[security-ml,The Git Security mailing list: git-security@googlegroups.com]
403
404
-As mentioned at the beginning of the section, patches that may be
405
-security relevant should not be submitted to the public mailing list
406
-mentioned below, but should instead be sent privately to the Git
407
-Security mailing list{security-ml-ref}.
404
+NOTE: Patches that may be
405
+security relevant should be submitted privately to the Git Security
406
+mailing list{security-ml}, instead of the public mailing list.
407
408
:contrib-scripts: footnoteref:[contrib-scripts,Scripts under `contrib/` are +
409
not part of the core `git` binary and must be called directly. Clone the Git +
@@ -431,12 +430,6 @@ Do not forget to add trailers such as `Acked-by:`, `Reviewed-by:` and
430
`Tested-by:` lines as necessary to credit people who helped your
431
patch, and "cc:" them when sending such a final version for inclusion.
432
434
-:security-ml: footnoteref:[security-ml,The Git Security mailing list: git-security@googlegroups.com]
435
-
436
-Before sending any patches, please note that patches that may be
437
-security relevant should be submitted privately to the Git Security
438
-mailing list{security-ml}, instead of the public mailing list.
439
-
433
Learn to use `format-patch` and `send-email` if possible. These commands
434
are optimized for the workflow of sending patches, avoiding many ways
435
your existing e-mail client (often optimized for "multipart/*" MIME