that starts with `-----BEGIN PGP SIGNED MESSAGE-----`. That is
not a text/plain, it's something else.
+ :security-ml-ref: footnoteref:[security-ml]
+
+ 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}.
+
Send your patch with "To:" set to the mailing list, with "cc:" listing
-people who are involved in the area you are touching (the output from
-`git blame $path` and `git shortlog --no-merges $path` would help to
+people who are involved in the area you are touching (the `git
+contacts` command in `contrib/contacts/` can help to
identify them), to solicit comments and reviews.
- :1: footnote:[The current maintainer: gitster@pobox.com]
- :2: footnote:[The mailing list: git@vger.kernel.org]
+ :current-maintainer: footnote:[The current maintainer: gitster@pobox.com]
+ :git-ml: footnote:[The mailing list: git@vger.kernel.org]
After the list reached a consensus that it is a good idea to apply the
- patch, re-send it with "To:" set to the maintainer{1} and "cc:" the
- list{2} for inclusion.
+ patch, re-send it with "To:" set to the maintainer{current-maintainer} and "cc:" the
+ list{git-ml} for inclusion.
Do not forget to add trailers such as `Acked-by:`, `Reviewed-by:` and
`Tested-by:` lines as necessary to credit people who helped your