This commit adds a mention to the '--subject-prefix' option in git-send-email's documentation. This option is already described in git-format-patch's docs (because it belongs to this command, actually), but it is very useful when you are submitting patches using git-send-email too, for obvious reasons. The text describing the option has been adapted from git-format-patch, in order to be "self-contained" and not mention other options that are not present in git-send-email's docs (e.g., '--numbered'). Signed-off-by: Sergio Durigan Junior <sergiodj@xxxxxxxxxxxx> --- Documentation/git-send-email.txt | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/Documentation/git-send-email.txt b/Documentation/git-send-email.txt index a60776e..76f531a 100644 --- a/Documentation/git-send-email.txt +++ b/Documentation/git-send-email.txt @@ -110,6 +110,13 @@ is not set, this will be prompted for. Only necessary if --compose is also set. If --compose is not set, this will be prompted for. +--subject-prefix=<Subject-Prefix>:: + Instead of the standard '[PATCH]' prefix in the subject + line, instead use '[<Subject-Prefix>]'. This is useful if you + are sending an RFC instead of a patch, or if the patch version + has been bumped (e.g., '[PATCH v2]'). See also + linkgit:git-format-patch[1]. + --to=<address>:: Specify the primary recipient of the emails generated. Generally, this will be the upstream maintainer of the project involved. Default is the -- 1.9.0 -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html