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 14:01:14 -0400 [thread overview]
Message-ID: <aJJG6ipsXIGXA6-p@lappy> (raw)
In-Reply-To: <cd9ecc4e0913ff9e012cf3c1f07c5920742eac24.camel@HansenPartnership.com>
On Tue, Aug 05, 2025 at 01:33:39PM -0400, James Bottomley wrote:
>On Tue, 2025-08-05 at 13:26 -0400, Sasha Levin wrote:
>> On Tue, Aug 05, 2025 at 12:49:02PM -0400, James Bottomley wrote:
>[...]
>> > 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?
>
>It seems to be mostly working for now, but what I often find is the
>header changes on a whim and the filter stops working. And, since
>nothing is written down, we all have to guess again what it means. If
>you're confident this one's not going to change, why not document it
>and commit to using it in the stable process docs?
It will probably need to be bigger than that: we'd need to document the
overall expectations and process before we document some of the nits in
it.
--
Thanks,
Sasha
next prev parent reply other threads:[~2025-08-05 18:01 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 [this message]
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=aJJG6ipsXIGXA6-p@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox