From: Steven Rostedt <rostedt@goodmis.org>
To: Willy Tarreau <w@1wt.eu>
Cc: "Jürgen Groß" <jgross@suse.com>,
"Konstantin Ryabitsev" <konstantin@linuxfoundation.org>,
"Joe Perches" <joe@perches.com>,
linux-kernel@vger.kernel.org, users@kernel.org
Subject: Re: [workflows]Re: [PATCH] get_maintainer: only use THE REST as a fallback
Date: Sat, 10 Oct 2026 21:21:09 -0400 [thread overview]
Message-ID: <20261010212109.202fd50d@226.227.38.69.naturalwireless.com> (raw)
In-Reply-To: <ask0dkduRV5pxeLZ@1wt.eu>
On Fri, 9 Oct 2026 20:37:42 +0200
Willy Tarreau <w@1wt.eu> wrote:
> I went into the same situation ~20 years ago, with filters sending LKML
> traffic into a dedicated folder, to then realize that I was no longer
> reading them because it requires to actively think about it and make an
> effort. So I turned this back to my normal folder and I can have a glance
> at them as messages arrive (like I'm seeing this one BTW).
>
> I understand the problem of volume on LKML that's not really compatible with
> 2k emails a day (nor with many people's expectations), but at the same time
> I think that a dedicated catch-all list with way less subscribers would be
> really nice for those who want to stay a bit informed of what's happening.
Agreed. I look at LKML every so often to see what's happening in the kernel.
If there is a catch all, could we make it only kernel patches. Tooling
patches (like my own trace-cmd patches) should not go to the kernel list.
I could then unsubscribe from LKML and subscribe to that instead.
-- Steve
next prev parent reply other threads:[~2026-10-11 1:21 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-08 12:51 Konstantin Ryabitsev
2026-10-08 13:03 ` Jason A. Donenfeld
2026-10-08 13:10 ` Konstantin Ryabitsev
2026-10-08 13:22 ` Matthieu Baerts
2026-10-08 14:05 ` Konstantin Ryabitsev
2026-10-08 16:04 ` Matthieu Baerts
2026-10-09 16:41 ` Jason A. Donenfeld
2026-10-09 22:25 ` Konstantin Ryabitsev
2026-10-08 13:15 ` Jürgen Groß
2026-10-08 14:02 ` Konstantin Ryabitsev
2026-10-09 12:24 ` Jason Gunthorpe
2026-10-09 18:37 ` Willy Tarreau
2026-10-11 1:21 ` Steven Rostedt [this message]
2026-10-09 23:35 ` Michael Kelley
2026-10-08 13:15 ` Michael S. Tsirkin
2026-10-08 13:39 ` Petr Pavlu
2026-10-08 14:06 ` Konstantin Ryabitsev
2026-10-09 16:25 ` Joe Perches
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=20261010212109.202fd50d@226.227.38.69.naturalwireless.com \
--to=rostedt@goodmis.org \
--cc=jgross@suse.com \
--cc=joe@perches.com \
--cc=konstantin@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=users@kernel.org \
--cc=w@1wt.eu \
/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
all inboxes | Powered by JetHome®