From: "Theodore Ts'o" <tytso@mit.edu>
To: Mark Brown <broonie@kernel.org>
Cc: Nick Desaulniers <ndesaulniers@google.com>,
Joe Perches <joe@perches.com>,
Konstantin Ryabitsev <konstantin@linuxfoundation.org>,
"Kernel.org Tools" <tools@linux.kernel.org>,
"# 3.4.x" <stable@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: get_maintainer, b4, and CC: stable
Date: Thu, 10 Aug 2023 12:01:52 -0400 [thread overview]
Message-ID: <20230810160152.GA2247938@mit.edu> (raw)
In-Reply-To: <6dabeab8-d013-40fc-a705-d2d202510549@sirena.org.uk>
On Wed, Aug 09, 2023 at 06:21:51PM +0100, Mark Brown wrote:
> On Wed, Aug 09, 2023 at 09:50:00AM -0700, Nick Desaulniers wrote:
>
> > I suspect that either b4 or get_maintainer could see the Fixes tag and
> > then suggest to Cc stable for me.
>
> > Should get_maintainer.pl make such recommendations?
>
> People use the Fixes tag all the time for bugs that never made it into a
> release...
I agree that it probably shouldn't.
Sometimes the bug was introduced by a commit that didn't have a Cc:
stable@kernel.org, but it gets automatically pulled into a LTS kernel
due to dependency reasons, or otherwise gets auto-selected into an LTS
kernel. So I try to add Fixes tags even for bugs that never make it
into the stable kernel --- but that doesn't mean that it should
automatically get a cc stable tag.
(Of course, it might be that the AUTOSEL process will automatically
pull in such commit, and then pull in something probably should not
been pulled into a stable tree, but this is why XFS has stable
backports maintainers --- because they don't trust the LTS automation.
For ext4, we probably see one of those sorts of the auto-backports
caused a regression maybe once a year? But that's a different
debate.)
- Ted
prev parent reply other threads:[~2023-08-10 16:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-09 16:50 get_maintainer, b4, and CC: stable Nick Desaulniers
2023-08-09 17:21 ` Mark Brown
2023-08-09 21:32 ` Joe Perches
2023-08-10 16:01 ` Theodore Ts'o [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=20230810160152.GA2247938@mit.edu \
--to=tytso@mit.edu \
--cc=broonie@kernel.org \
--cc=joe@perches.com \
--cc=konstantin@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ndesaulniers@google.com \
--cc=stable@vger.kernel.org \
--cc=tools@linux.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.