From: Greg KH <gregkh@linuxfoundation.org>
To: David Rientjes <rientjes@google.com>
Cc: Aaro Koskinen <aaro.koskinen@iki.fi>,
"Theodore Ts'o" <tytso@mit.edu>,
Linux Kernel Developers List <linux-kernel@vger.kernel.org>,
linux-doc@vger.kernel.org
Subject: Re: [PATCH] Documentation: talk about "Cc: stable@vger.kernel.org"
Date: Mon, 9 Jul 2012 07:42:34 -0700 [thread overview]
Message-ID: <20120709144234.GA3487@kroah.com> (raw)
In-Reply-To: <alpine.DEB.2.00.1207090345540.8224@chino.kir.corp.google.com>
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 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.
> >
> > 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: stable@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
prev parent reply other threads:[~2012-07-09 14:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-06 21:38 [PATCH] Documentation: talk about "Cc: stable@vger.kernel.org" Theodore Ts'o
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 [this message]
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=20120709144234.GA3487@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=aaro.koskinen@iki.fi \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rientjes@google.com \
--cc=tytso@mit.edu \
/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