From: "Theodore Ts'o" <tytso@mit.edu>
To: Linux Kernel Developers List <linux-kernel@vger.kernel.org>,
linux-doc@vger.kernel.org
Cc: gregkh@linuxfoundation.org, "Theodore Ts'o" <tytso@mit.edu>
Subject: [PATCH] Documentation: talk about "Cc: stable@vger.kernel.org"
Date: Fri, 6 Jul 2012 17:38:50 -0400 [thread overview]
Message-ID: <1341610730-6277-1-git-send-email-tytso@mit.edu> (raw)
I couldn't remember whether the canonical marking is stable@kernel.org
or stable@vger.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@mit.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@vger.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
next reply other threads:[~2012-07-06 21:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-06 21:38 Theodore Ts'o [this message]
2012-07-06 21:59 ` Aaro Koskinen
2012-07-06 22:01 ` Theodore Ts'o
2012-07-09 10:48 ` David Rientjes
2012-07-09 14:42 ` Greg KH
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1341610730-6277-1-git-send-email-tytso@mit.edu \
--to=tytso@mit.edu \
--cc=gregkh@linuxfoundation.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®