Documentation/SubmittingPatches: Instruct how to use [PATCH] Subject header
Signed-off-by: Junio C Hamano <gitster@pobox.com>
Junio C Hamano committed
Feb 3, 2008 at 16:55 UTC
4e891acf679c0020b61889447f8f412324aeffa9
1 file changed
+6
-1
Documentation/SubmittingPatches
+6
-1
@@ -112,7 +112,12 @@ lose tabs that way if you are not careful.
112
113
It is a common convention to prefix your subject line with
114
[PATCH]. This lets people easily distinguish patches from other
115
-e-mail discussions.
115
+e-mail discussions. Use of additional markers after PATCH and
116
+the closing bracket to mark the nature of the patch is also
117
+encouraged. E.g. [PATCH/RFC] is often used when the patch is
118
+not ready to be applied but it is for discussion, [PATCH v2],
119
+[PATCH v3] etc. are often seen when you are sending an update to
120
+what you have previously sent.
121
122
"git format-patch" command follows the best current practice to
123
format the body of an e-mail message. At the beginning of the