From: "Theodore Y. Ts'o" <tytso@mit.edu>
To: Jiri Kosina <jikos@kernel.org>
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 13:37:47 -0400 [thread overview]
Message-ID: <20181023173747.GG6850@thunk.org> (raw)
In-Reply-To: <alpine.LRH.2.00.1810231833260.2860@gjva.wvxbf.pm>
On Tue, Oct 23, 2018 at 06:36:26PM +0200, Jiri Kosina wrote:
> 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.
Ah, I didn't get that you were trying to suggest that things only go
into stable if it has both Fixes: *and* Cc: Stable.
If that's the problem you were trying to solve, perhaps we could ask
Stephen Rothwell if he would be willing to run a script that sends
nag-o-grams to Maintainers who incluce patches in linux-next that have
Cc: stable but neither Fixes nor a "# 4.x" appended to the end of the
Cc: stable line?
- Ted
next prev parent reply other threads:[~2018-10-23 17:37 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
2018-10-23 17:37 ` Theodore Y. Ts'o [this message]
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=20181023173747.GG6850@thunk.org \
--to=tytso@mit.edu \
--cc=Larry.Finger@lwfinger.net \
--cc=gregkh@linuxfoundation.org \
--cc=jikos@kernel.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