[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <1473277661.29864.25.camel@perches.com>
Date: Wed, 07 Sep 2016 12:47:41 -0700
From: Joe Perches <joe@...ches.com>
To: Lee Jones <lee.jones@...aro.org>
Cc: Russell King - ARM Linux <linux@...linux.org.uk>,
lkml <linux-kernel@...r.kernel.org>,
Jonathan Corbet <corbet@....net>
Subject: rfc: Updating SubmittingPatches with [RFC PATCH] and/or [WIP PATCH]
On Wed, 2016-09-07 at 17:38 +0100, Lee Jones wrote:
> On Wed, 07 Sep 2016, Joe Perches wrote:
[]
> > And another patch series prefix that could be used
> > instead of RFC is WIP.
> Certainly sounds reasonable. Is there a difference in the meaning?
Request for Comment and Work In Progress differences:
Maybe add something like this to Documentation/SubmittingPatches
---
Documentation/SubmittingPatches | 6 ++++++
1 file changed, 6 insertions(+)
diff --git a/Documentation/SubmittingPatches b/Documentation/SubmittingPatches
index 8c79f1d..aa76057 100644
--- a/Documentation/SubmittingPatches
+++ b/Documentation/SubmittingPatches
@@ -404,6 +404,12 @@ convention to prefix your subject line with [PATCH]. This
and other kernel developers more easily distinguish patches from other
e-mail discussions.
+If the patch or patch series is just a proposal to garner comments
+use [RFC PATCH] before each patch subject.
+
+If the patch or patch seriies is incomplete or possibly contains known
+defects and you would like others to see the work to date use
+[WIP PATCH] before each patch subject.
11) Sign your work
Powered by blists - more mailing lists