From: Jiri Kosina <jikos@kernel.org>
To: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Cc: Theodore Ts'o <tytso@mit.edu>,
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 20:08:21 +0200 (CEST) [thread overview]
Message-ID: <nycvar.YFH.7.76.1810232007500.23511@cbobk.fhfr.pm> (raw)
In-Reply-To: <CAKdAkRQvwe93nwLgEQuSsmbUbzMzVjO22wrfg=wzQtfHoSq2DA@mail.gmail.com>
On Tue, 23 Oct 2018, Dmitry Torokhov wrote:
> > 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?
> >
>
> Patches adding new PCI/USB/ACPI IDs or DMI quirks are usually accepted
> into stable but normally lack "Fixes" tag.
That could easily be made an easily identifiable exception to the rule
though.
--
Jiri Kosina
SUSE Labs
prev parent reply other threads:[~2018-10-23 18:08 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
2018-10-23 18:05 ` Dmitry Torokhov
2018-10-23 18:08 ` Jiri Kosina [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=nycvar.YFH.7.76.1810232007500.23511@cbobk.fhfr.pm \
--to=jikos@kernel.org \
--cc=Larry.Finger@lwfinger.net \
--cc=dmitry.torokhov@gmail.com \
--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;
as well as URLs for NNTP newsgroup(s).