Linux wireless drivers development
 help / color / mirror / Atom feed
From: Jiri Kosina <jikos@kernel.org>
To: "Theodore Y. Ts'o" <tytso@mit.edu>
Cc: Larry Finger <Larry.Finger@lwfinger.net>,
	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 18:36:26 +0200 (CEST)	[thread overview]
Message-ID: <alpine.LRH.2.00.1810231833260.2860@gjva.wvxbf.pm> (raw)
In-Reply-To: <20181023143856.GD6850@thunk.org>

On Tue, 23 Oct 2018, Theodore Y. Ts'o wrote:

> > 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.

FWIW, I brought this up already at KS 2016, see Jon's coverage here:

	https://lwn.net/Articles/705220/

My primary motivation to bring that up back then was to try to reduce the 
number of patches that are taken into -stable while there is no good 
justification for that (by requiring each and every of those having Fixes: 
present as a requirement), but it didn't really lead anywhere.

-- 
Jiri Kosina
SUSE Labs

  reply	other threads:[~2018-10-23 17:02 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
2018-10-23 16:36   ` Jiri Kosina [this message]
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=alpine.LRH.2.00.1810231833260.2860@gjva.wvxbf.pm \
    --to=jikos@kernel.org \
    --cc=Larry.Finger@lwfinger.net \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --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