[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <1341610730-6277-1-git-send-email-tytso@mit.edu>
Date: Fri, 6 Jul 2012 17:38:50 -0400
From: Theodore Ts'o <tytso@....edu>
To: Linux Kernel Developers List <linux-kernel@...r.kernel.org>,
linux-doc@...r.kernel.org
Cc: gregkh@...uxfoundation.org, Theodore Ts'o <tytso@....edu>
Subject: [PATCH] Documentation: talk about "Cc: stable@...r.kernel.org"
I couldn't remember whether the canonical marking is stable@...nel.org
or stable@...r.kernel.org, so I went looking, and discovered that it
wasn't mentioned in the kernel sources. You can find mention of it in
Greg K-H's blog, but not everyone would necessarily find this blog
entry.
Signed-off-by: "Theodore Ts'o" <tytso@....edu>
---
Documentation/SubmittingPatches | 8 +++++++-
1 file changed, 7 insertions(+), 1 deletion(-)
diff --git a/Documentation/SubmittingPatches b/Documentation/SubmittingPatches
index c379a2a..d802ee2 100644
--- a/Documentation/SubmittingPatches
+++ b/Documentation/SubmittingPatches
@@ -418,7 +418,13 @@ If a person has had the opportunity to comment on a patch, but has not
provided such comments, you may optionally add a "Cc:" tag to the patch.
This is the only tag which might be added without an explicit action by the
person it names. This tag documents that potentially interested parties
-have been included in the discussion
+have been included in the discussion.
+
+If a patch is a bug fix which you believe should be backported to the
+stable kernel trees, you should add a simple "Cc: stable@...r.kernel.org>"
+marking in the Signed-off-by: area. Once the patch hits Linus's tree,
+the patch will be automatically applied to the currently active stable
+trees if possible. If it does not apply, you will be notified of that fact.
14) Using Reported-by:, Tested-by: and Reviewed-by:
--
1.7.11.1.108.gb129051
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists