From: Greg KH <gregkh@linuxfoundation.org>
To: Steve French <smfrench@gmail.com>
Cc: Stable <stable@vger.kernel.org>, LKML <linux-kernel@vger.kernel.org>
Subject: Re: "Fixes:" vs. "Cc: stable ..."
Date: Wed, 24 Aug 2022 19:58:19 +0200 [thread overview]
Message-ID: <YwZmu1ZTbjVqIY/C@kroah.com> (raw)
In-Reply-To: <CAH2r5muO1OkOV0jjJo89Zpvj43u_X95smuujg66-emQFgSXfgQ@mail.gmail.com>
On Wed, Aug 24, 2022 at 12:14:12PM -0500, Steve French wrote:
> Do changesets that already included the "Fixes:" tag in the commit
> description also need to include the "Cc: stable@vger.kernel.org" in
> order to be included in stable?
As per the documentation:
https://www.kernel.org/doc/html/latest/process/stable-kernel-rules.html
You should be putting cc: stable@... on the patch.
But as not all maintainers do, we have to dig through those with Fixes:
in order to actually catch all bugfixes :(
So please, use cc: stable.
thanks,
greg k-h
next prev parent reply other threads:[~2022-08-24 17:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-24 17:14 "Fixes:" vs. "Cc: stable ..." Steve French
2022-08-24 17:58 ` Greg KH [this message]
2022-08-24 18:11 ` Steve French
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=YwZmu1ZTbjVqIY/C@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=smfrench@gmail.com \
--cc=stable@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;
as well as URLs for NNTP newsgroup(s).