[PATCH] Documentation: talk about "Cc: sta...@vger.kernel.org"
I couldn't remember whether the canonical marking is sta...@kernel.org or sta...@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" --- 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: sta...@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 -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [PATCH] Documentation: talk about "Cc: sta...@vger.kernel.org"
Hi, On Fri, Jul 06, 2012 at 05:38:50PM -0400, Theodore Ts'o wrote: > I couldn't remember whether the canonical marking is sta...@kernel.org > or sta...@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. It's documented in Documentation/stable_kernel_rules.txt. A. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [PATCH] Documentation: talk about "Cc: sta...@vger.kernel.org"
On Sat, Jul 07, 2012 at 12:59:44AM +0300, Aaro Koskinen wrote: > Hi, > > On Fri, Jul 06, 2012 at 05:38:50PM -0400, Theodore Ts'o wrote: > > I couldn't remember whether the canonical marking is sta...@kernel.org > > or sta...@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. > > It's documented in Documentation/stable_kernel_rules.txt. Ah, so it is. I don't know how I missed that! - Ted -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [PATCH] Documentation: talk about "Cc: sta...@vger.kernel.org"
On Sat, 7 Jul 2012, Aaro Koskinen wrote: > > I couldn't remember whether the canonical marking is sta...@kernel.org > > or sta...@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. > > It's documented in Documentation/stable_kernel_rules.txt. > I'm wondering if it would be helpful to the stable maintainers if we explicitly asked that patches including "Cc: sta...@vger.kernel.org" also include the version number of the earliest version that the change should be backported to? Andrew and others do this quite often with Cc: sta...@vger.kernel.org [3.2+] so perhaps such a convention should be added to the documentation? -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [PATCH] Documentation: talk about "Cc: sta...@vger.kernel.org"
On Mon, Jul 09, 2012 at 03:48:14AM -0700, David Rientjes wrote: > On Sat, 7 Jul 2012, Aaro Koskinen wrote: > > > > I couldn't remember whether the canonical marking is sta...@kernel.org > > > or sta...@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. > > > > It's documented in Documentation/stable_kernel_rules.txt. > > > > I'm wondering if it would be helpful to the stable maintainers if we > explicitly asked that patches including "Cc: sta...@vger.kernel.org" also > include the version number of the earliest version that the change should > be backported to? It can be helpful, and in fact, is what is described in the above file already, although it is often overlooked as it is only part of an example. But really, it's usually not needed, I'm more interested in getting more maintainers to actually start marking patches for stable, that's the larger problem we are dealing with. Sorting out after-the-fact which kernel version a patch is to be applied to is much simpler than finding the patches in the first place. thanks, greg k-h -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
