mirror of
https://github.com/git/git.git
synced 2024-05-10 07:16:09 +02:00
SubmittingPatches: dedupe discussion of security patches
Signed-off-by: Linus Arver <linusa@google.com> Signed-off-by: Junio C Hamano <gitster@pobox.com>
This commit is contained in:
parent
e2663c4597
commit
01ea2b2836
|
@ -399,12 +399,11 @@ letter.
|
|||
|
||||
==== Choosing your reviewers
|
||||
|
||||
:security-ml-ref: footnoteref:[security-ml]
|
||||
:security-ml: footnoteref:[security-ml,The Git Security mailing list: git-security@googlegroups.com]
|
||||
|
||||
As mentioned at the beginning of the section, patches that may be
|
||||
security relevant should not be submitted to the public mailing list
|
||||
mentioned below, but should instead be sent privately to the Git
|
||||
Security mailing list{security-ml-ref}.
|
||||
NOTE: Patches that may be
|
||||
security relevant should be submitted privately to the Git Security
|
||||
mailing list{security-ml}, instead of the public mailing list.
|
||||
|
||||
:contrib-scripts: footnoteref:[contrib-scripts,Scripts under `contrib/` are +
|
||||
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
|
|||
`Tested-by:` lines as necessary to credit people who helped your
|
||||
patch, and "cc:" them when sending such a final version for inclusion.
|
||||
|
||||
:security-ml: footnoteref:[security-ml,The Git Security mailing list: git-security@googlegroups.com]
|
||||
|
||||
Before sending any patches, please note that patches that may be
|
||||
security relevant should be submitted privately to the Git Security
|
||||
mailing list{security-ml}, instead of the public mailing list.
|
||||
|
||||
Learn to use `format-patch` and `send-email` if possible. These commands
|
||||
are optimized for the workflow of sending patches, avoiding many ways
|
||||
your existing e-mail client (often optimized for "multipart/*" MIME
|
||||
|
|
Loading…
Reference in New Issue