path: root/Documentation/SubmittingPatches
diff options
authorJunio C Hamano <>2008-02-04 00:55:21 (GMT)
committerJunio C Hamano <>2008-02-05 08:39:03 (GMT)
commit4e891acf679c0020b61889447f8f412324aeffa9 (patch)
treeadea632f49a6816c2af8507b6d25f3a3a4ed9e18 /Documentation/SubmittingPatches
parent7a2078b4b00fb1c5d7b0bf8155778f79377b8f2f (diff)
Documentation/SubmittingPatches: Instruct how to use [PATCH] Subject header
Signed-off-by: Junio C Hamano <>
Diffstat (limited to 'Documentation/SubmittingPatches')
1 files changed, 6 insertions, 1 deletions
diff --git a/Documentation/SubmittingPatches b/Documentation/SubmittingPatches
index de08d09..cd80148 100644
--- a/Documentation/SubmittingPatches
+++ b/Documentation/SubmittingPatches
@@ -112,7 +112,12 @@ 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.
+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
format the body of an e-mail message. At the beginning of the