From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: Jiri Kosina <jikos@kernel.org>
Cc: Greg KH <gregkh@linuxfoundation.org>,
James Bottomley <James.Bottomley@hansenpartnership.com>,
ksummit@lists.linux.dev
Subject: Re: [MAINTAINERS SUMMIT] The amount of -stable emails
Date: Tue, 05 Aug 2025 18:34:12 -0400 [thread overview]
Message-ID: <yq134a5ctxw.fsf@ca-mkp.ca.oracle.com> (raw)
In-Reply-To: <p1886464-9p9n-4p0r-52r7-70sqprsoo32q@xreary.bet> (Jiri Kosina's message of "Tue, 5 Aug 2025 23:39:58 +0200 (CEST)")
Jiri,
>> You can also filter on stable-commits@vger.kernel.org, which is what I
>> do locally.
>>
>> So filter away!
>
> The question is whether it's really worth all the e-mail traffic this is
> generating, if people are just filtering those away.
If I explicitly tagged a commit for stable and it applies without any
problems, I would prefer not to hear about it.
When I am micromanaging a particular patch (critical bug or security
fix), I am much more likely to be poking around in git instead of
relying on email notifications to determine whether it has been applied
or not.
I do have interest in failures, however. Obviously the patch author
should be the first point of contact. But I do like to get copied on
backport failure notifications. While I may not act on these, I do like
having insight into what is going on...
--
Martin K. Petersen
next prev parent reply other threads:[~2025-08-05 22:34 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
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 [this message]
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=yq134a5ctxw.fsf@ca-mkp.ca.oracle.com \
--to=martin.petersen@oracle.com \
--cc=James.Bottomley@hansenpartnership.com \
--cc=gregkh@linuxfoundation.org \
--cc=jikos@kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox