From: "Theodore Y. Ts'o" <tytso@mit.edu>
To: Larry Finger <Larry.Finger@lwfinger.net>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
LKML <linux-kernel@vger.kernel.org>,
linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: Is Fixes line enough?
Date: Tue, 23 Oct 2018 10:38:56 -0400 [thread overview]
Message-ID: <20181023143856.GD6850@thunk.org> (raw)
In-Reply-To: <a99840d5-7d57-ec1f-1c70-37ffa6cfd31b@lwfinger.net>
On Tue, Oct 23, 2018 at 09:05:20AM -0500, Larry Finger wrote:
> Greg,
>
> A question has come up on the linux-wireless ML. If a patch has a "Fixes"
> line, is that sufficient to get it flagged as a patch in Stable, or is a
> "Cc: Stable" line also needed?
Someone actually asked this question at the Maintainer's Summit,
actually. The answer was that the Fixes line is not sufficient for
Greg's scripts; you have to have the "Cc: stable" line as well. Greg
tried using the Fixes line as a trigger, but there were too many cases
where this pulled in commits that weren't really suitable for the
Stable kernels. Sasha's machine-learning lash up will use the Fixes
line as a signal, but if you want to explicitly request that the patch
should be cherry-picked into Stable, you should have the "Cc: stable"
line.
(Also mentioned that at the Maintainer's Summit was that we probably
do need to take a look at the Stable documentation and see how it
needs to be updated to reflect how things are currently behind
handled. :-)
Cheers,
- Ted
next prev parent reply other threads:[~2018-10-23 14:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-23 14:05 Is Fixes line enough? Larry Finger
2018-10-23 14:34 ` Greg Kroah-Hartman
2018-10-23 14:38 ` Theodore Y. Ts'o [this message]
2018-10-23 16:36 ` Jiri Kosina
2018-10-23 17:37 ` Theodore Y. Ts'o
2018-10-23 18:05 ` Dmitry Torokhov
2018-10-23 18:08 ` Jiri Kosina
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=20181023143856.GD6850@thunk.org \
--to=tytso@mit.edu \
--cc=Larry.Finger@lwfinger.net \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@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