diff options
| author | Junio C Hamano <gitster@pobox.com> | 2017-11-21 14:32:50 +0900 |
|---|---|---|
| committer | Junio C Hamano <gitster@pobox.com> | 2017-11-21 14:32:50 +0900 |
| commit | d71056015c147557a3bbf069107d9470c0579974 (patch) | |
| tree | d0c7f5e5eadff0e2a9ac89dd21a81607be7222e2 /SubmittingPatches.txt | |
| parent | b72f60303287a25c0a0305120b203276faca07fa (diff) | |
| download | git-htmldocs-d71056015c147557a3bbf069107d9470c0579974.tar.gz | |
Autogenerated HTML docs for v2.15.0-317-g14c63
Diffstat (limited to 'SubmittingPatches.txt')
| -rw-r--r-- | SubmittingPatches.txt | 21 |
1 files changed, 13 insertions, 8 deletions
diff --git a/SubmittingPatches.txt b/SubmittingPatches.txt index 17419f790..3ef30922e 100644 --- a/SubmittingPatches.txt +++ b/SubmittingPatches.txt @@ -203,14 +203,15 @@ lose tabs that way if you are not careful. It is a common convention to prefix your subject line with [PATCH]. This lets people easily distinguish patches from other -e-mail discussions. Use of additional markers after PATCH and -the closing bracket to mark the nature of the patch is also -encouraged. E.g. [PATCH/RFC] is often used when the patch is -not ready to be applied but it is for discussion, [PATCH v2], -[PATCH v3] etc. are often seen when you are sending an update to -what you have previously sent. - -`git format-patch` command follows the best current practice to +e-mail discussions. Use of markers in addition to PATCH within +the brackets to describe the nature of the patch is also +encouraged. E.g. [RFC PATCH] (where RFC stands for "request for +comments") is often used to indicate a patch needs further +discussion before being accepted, [PATCH v2], [PATCH v3] etc. +are often seen when you are sending an update to what you have +previously sent. + +The `git format-patch` command follows the best current practice to format the body of an e-mail message. At the beginning of the patch should come your commit message, ending with the Signed-off-by: lines, and a line that consists of three dashes, @@ -218,6 +219,10 @@ followed by the diffstat information and the patch itself. If you are forwarding a patch from somebody else, optionally, at the beginning of the e-mail message just before the commit message starts, you can put a "From: " line to name that person. +To change the default "[PATCH]" in the subject to "[<text>]", use +`git format-patch --subject-prefix=<text>`. As a shortcut, you +can use `--rfc` instead of `--subject-prefix="RFC PATCH"`, or +`-v <n>` instead of `--subject-prefix="PATCH v<n>"`. You often want to add additional explanation about the patch, other than the commit message itself. Place such "cover letter" |