From: Junio C Hamano Date: Tue, 21 Nov 2017 05:07:51 +0000 (+0900) Subject: Merge branch 'ad/submitting-patches-title-decoration' X-Git-Tag: v2.16.0-rc0~110 X-Git-Url: https://granicus.if.org/sourcecode?a=commitdiff_plain;h=1a5f2e44312e52d93edead612ea692cfc5c90c3b;p=git Merge branch 'ad/submitting-patches-title-decoration' Doc update around use of "format-patch --subject-prefix" etc. * ad/submitting-patches-title-decoration: doc/SubmittingPatches: correct subject guidance --- 1a5f2e44312e52d93edead612ea692cfc5c90c3b diff --cc Documentation/SubmittingPatches index 17419f7901,89f2390716..3ef30922ec --- a/Documentation/SubmittingPatches +++ b/Documentation/SubmittingPatches @@@ -203,14 -184,15 +203,15 @@@ lose tabs that way if you are not caref 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 ++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,