From: Sasha Levin <sashal@kernel.org>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Mark Brown <broonie@kernel.org>, Jiri Kosina <jkosina@suse.com>,
ksummit@lists.linux.dev
Subject: Re: [MAINTAINERS SUMMIT] The amount of -stable emails
Date: Tue, 5 Aug 2025 13:14:24 -0400 [thread overview]
Message-ID: <aJI78KDWGq35K6W-@lappy> (raw)
In-Reply-To: <20250805122828.68312a8d@gandalf.local.home>
On Tue, Aug 05, 2025 at 12:28:28PM -0400, Steven Rostedt wrote:
>On Tue, 5 Aug 2025 17:08:44 +0100
>Mark Brown <broonie@kernel.org> wrote:
[snip]
>Now, if something is marked for stable, I really don't want to be bothered
>that it made it to a stable tree. If I marked something for stable, sending
>me an email that it was applied is rather redundant.
So I'd love to cancel the "Added to the stable tree" mails. I honestly
don't even know why they go out: my understanding that it was for
historical reasons where someone asked for those in the past, but I
really feel bad about sending those out because to me they are pure
spam.
>> One thing I'd really like to see there would be to avoid sending each
>> patch separately for every stable version, that just blows up the mail
>> volume hugely especially for those of us with subsystems that carry a
>> lot of quirks. I'm sure the range of versions something is being pulled
>> back to could be expressed in a single mail instead, it's always some
>> range of versions being processed en masse rather than just a single
>> version. The per version cover letter is more useful for replying with
>> test results but that doesn't need the whole series.
>
>Yes, I agree that a digest of all the autoselects would be good.
I actually did that earlier today!
See the latest batch of AUTOSELs: https://lore.kernel.org/stable/20250805130945.471732-1-sashal@kernel.org/T/#t
Instead of one mail per tree, the subject line contains the range of
trees it applies to.
--
Thanks,
Sasha
next prev parent reply other threads:[~2025-08-05 17:14 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-05 15:38 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 [this message]
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
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=aJI78KDWGq35K6W-@lappy \
--to=sashal@kernel.org \
--cc=broonie@kernel.org \
--cc=jkosina@suse.com \
--cc=ksummit@lists.linux.dev \
--cc=rostedt@goodmis.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