From: Sasha Levin <sashal@kernel.org>
To: James Bottomley <James.Bottomley@hansenpartnership.com>
Cc: Jiri Kosina <jkosina@suse.com>, ksummit@lists.linux.dev
Subject: Re: [MAINTAINERS SUMMIT] The amount of -stable emails
Date: Tue, 5 Aug 2025 13:26:24 -0400 [thread overview]
Message-ID: <aJI-wBgmE8LoTyyZ@lappy> (raw)
In-Reply-To: <cb91ddf05b9ea48056765a9027ff9132e080df30.camel@HansenPartnership.com>
On Tue, Aug 05, 2025 at 12:49:02PM -0400, James Bottomley wrote:
>On Tue, 2025-08-05 at 17:38 +0200, Jiri Kosina wrote:
>> This proposal is coming as a followup to the brief IRC discussion
>> that happened a few months back.
>>
>> The amount of e-mails that are coming (with maintainers directly
>> CCed) as a result of patches being merged to -stable is so
>> overwhelming that I am not sure that people are making any productive
>> use of it whatsoever.
>>
>> I am personally pretty much ignoring most of it, as (a) I wouldn't
>> have time to do anything else otherwise (b) I don't have a sufficient
>> motivation / time to invest effort into stable in the fist place.
>>
>> I feel it'd be beneficial to discuss this, and (depending on the
>> outcome)perhaps make it opt-in (or opt-out) at least, with
>> people/subsystems having means how to be excluded from all that ...
>> ?
>
>Actually, if stable emails just had a header tag, it would be easy for
>procmail to sort them out ... which is what I've been asking for for
>years. X-Stable-Base: and X-Stable: seem to be reasonably common and
>catch most of it, but codifying the use in the kernel documentation and
>using them consistently would really help.
Do we have any stable-related mails that don't have an X-Stable: header?
--
Thanks,
Sasha
next prev parent reply other threads:[~2025-08-05 17:26 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-05 15:38 [MAINTAINERS SUMMIT] The amount of -stable emails Jiri Kosina
2025-08-05 16:08 ` Mark Brown
2025-08-05 16:28 ` Steven Rostedt
2025-08-05 16:41 ` Mark Brown
2025-08-06 8:04 ` Geert Uytterhoeven
2025-08-06 10:42 ` Mark Brown
2025-08-06 12:20 ` Sasha Levin
2025-08-06 12:24 ` Mark Brown
2025-08-06 14:57 ` Theodore Ts'o
2025-08-06 21:35 ` Sasha Levin
2025-08-05 17:14 ` Sasha Levin
2025-08-05 17:59 ` Konstantin Ryabitsev
2025-08-05 21:04 ` Sasha Levin
2025-08-05 17:40 ` Chuck Wolber
2025-08-05 16:49 ` James Bottomley
2025-08-05 17:26 ` Sasha Levin [this message]
2025-08-05 17:33 ` James Bottomley
2025-08-05 18:01 ` Sasha Levin
2025-08-06 8:04 ` Greg KH
2025-08-05 17:34 ` Greg KH
2025-08-05 21:39 ` Jiri Kosina
2025-08-05 22:34 ` Martin K. Petersen
2025-08-06 5:44 ` Tomasz Figa
2025-08-06 6:27 ` Takashi Iwai
2025-08-06 7:00 ` Jiri Kosina
2025-08-06 7:08 ` Takashi Iwai
2025-08-12 17:19 ` Steven Rostedt
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=aJI-wBgmE8LoTyyZ@lappy \
--to=sashal@kernel.org \
--cc=James.Bottomley@hansenpartnership.com \
--cc=jkosina@suse.com \
--cc=ksummit@lists.linux.dev \
/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.