From: "Theodore Y. Ts'o" <tytso@mit.edu>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Sasha Levin <sashal@kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Michal Hocko <mhocko@kernel.org>, Hugh Dickins <hughd@google.com>,
Linus Torvalds <torvalds@linux-foundation.org>,
Mike Kravetz <mike.kravetz@oracle.com>,
Miaohe Lin <linmiaohe@huawei.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux MM <linux-mm@kvack.org>, stable <stable@vger.kernel.org>
Subject: Re: 5.13.2-rc and others have many not for stable
Date: Thu, 15 Jul 2021 10:47:02 -0400 [thread overview]
Message-ID: <YPBKZnWfK08PWarN@mit.edu> (raw)
In-Reply-To: <CAMuHMdUi+HsApqRwBDBFnfnAOs9EprDh5HCV4UncEL_cnXZasA@mail.gmail.com>
On Thu, Jul 15, 2021 at 11:01:04AM +0200, Geert Uytterhoeven wrote:
> > Because cc: stable came first, and for some reason people think that it
> > is all that is necessary to get patches committed to the stable tree,
> > despite it never being documented or that way. I have to correct
> > someone about this about 2x a month on the stable@vger list.
>
> For a developer, it's much easier to not care about "Cc: stable"
> at all, because as soon as you add a "Cc: stable" to a patch, or CC
> stable, someone will compain ;-) Much easier to just add a Fixes: tag,
> and know it will be backported to trees that have the "buggy" commit.
What sort of complaints have you gotten? I add "cc: stable" for the
ext4 tree, and I can't say I've gotten any complaints.
- Ted
next prev parent reply other threads:[~2021-07-15 14:47 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-13 5:55 Hugh Dickins
2021-07-13 6:31 ` Greg Kroah-Hartman
2021-07-13 7:20 ` Greg Kroah-Hartman
2021-07-14 1:28 ` Andrew Morton
2021-07-14 7:24 ` Jiri Slaby
2021-07-14 7:52 ` Michal Hocko
2021-07-14 15:30 ` Sasha Levin
2021-07-15 7:07 ` Michal Hocko
2021-07-15 15:57 ` Justin Forbes
2021-07-14 9:18 ` Greg Kroah-Hartman
2021-07-14 13:23 ` Greg Kroah-Hartman
2021-07-14 21:09 ` Andrew Morton
2021-07-15 10:39 ` Mel Gorman
2021-07-14 13:52 ` Sasha Levin
2021-07-14 15:35 ` Theodore Y. Ts'o
2021-07-14 15:43 ` Greg Kroah-Hartman
2021-07-14 15:46 ` Greg Kroah-Hartman
2021-07-14 17:21 ` Theodore Y. Ts'o
2021-07-14 17:34 ` Greg Kroah-Hartman
2021-07-15 9:01 ` Geert Uytterhoeven
2021-07-15 14:47 ` Theodore Y. Ts'o [this message]
2021-07-15 15:03 ` Geert Uytterhoeven
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=YPBKZnWfK08PWarN@mit.edu \
--to=tytso@mit.edu \
--cc=akpm@linux-foundation.org \
--cc=geert@linux-m68k.org \
--cc=gregkh@linuxfoundation.org \
--cc=hughd@google.com \
--cc=linmiaohe@huawei.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@kernel.org \
--cc=mike.kravetz@oracle.com \
--cc=sashal@kernel.org \
--cc=stable@vger.kernel.org \
--cc=torvalds@linux-foundation.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