From: Sasha Levin <sashal@kernel.org>
To: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
Cc: Steven Rostedt <rostedt@goodmis.org>,
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 17:04:27 -0400 [thread overview]
Message-ID: <aJJx21BMlFIN7KO7@lappy> (raw)
In-Reply-To: <20250805-mottled-granite-otter-3dadde@lemur>
On Tue, Aug 05, 2025 at 01:59:10PM -0400, Konstantin Ryabitsev wrote:
>On Tue, Aug 05, 2025 at 01:14:24PM -0400, Sasha Levin wrote:
>> > 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.
>
>I can suggest that you write them to a public-inbox feed instead. We can then
>pull that into lore so they still show up for people performing context
>queries, but we don't ever deliver them via SMTP.
I wish I knew who actually uses it, so maybe we could just drop it
altogether :/
This predates the lei/lore days, so I'm a git concerned about making a
change like that if anyone is actually relying on those mails.
--
Thanks,
Sasha
next prev parent reply other threads:[~2025-08-05 21:04 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 [this message]
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=aJJx21BMlFIN7KO7@lappy \
--to=sashal@kernel.org \
--cc=broonie@kernel.org \
--cc=jkosina@suse.com \
--cc=konstantin@linuxfoundation.org \
--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 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.