[PATCH] Documentation/SubmittingPatches: Instruct how to use [PATCH] Subject header
From: Jari Aalto <hidden>
Date: 2016-06-15 22:44:10
Subsystem:
documentation, the rest · Maintainers:
Jonathan Corbet, Linus Torvalds
Suggest putting additional message inside brackets, like [PATCH v2] for reworked content. Signed-off-by: Jari Aalto <jari.aalto AT cante.net> --- Idea by Jakub Narebski Documentation/SubmittingPatches | 3 +++ 1 files changed, 3 insertions(+), 0 deletions(-)
diff --git a/Documentation/SubmittingPatches b/Documentation/SubmittingPatches
index de08d09..69ecbd3 100644
--- a/Documentation/SubmittingPatches
+++ b/Documentation/SubmittingPatches@@ -37,6 +37,9 @@ Checklist (and a short version for the impatient): maintainer (gitster@pobox.com). If you use git-send-email(1), please test it first by sending email to yourself. + - If you rework the patch, announce the message + in brackets. For example "[PATCH/RFC]", "[PATCH (resend)]", + "[PATCH v2]" etc. Long version:
--
1.5.4-rc5.GIT-dirty
--
Welcome to FOSS revolution: we fix and modify until it shines