From: Willy Tarreau <w@1wt.eu>
To: "Jürgen Groß" <jgross@suse.com>
Cc: Konstantin Ryabitsev <konstantin@linuxfoundation.org>,
Joe Perches <joe@perches.com>,
linux-kernel@vger.kernel.org, users@kernel.org
Subject: Re: [PATCH] get_maintainer: only use THE REST as a fallback
Date: Fri, 9 Oct 2026 20:37:42 +0200 [thread overview]
Message-ID: <ask0dkduRV5pxeLZ@1wt.eu> (raw)
In-Reply-To: <8e194f64-6add-4fb3-a1bb-9b27719b409e@suse.com>
On Thu, Oct 08, 2026 at 03:15:03PM +0200, Jürgen Groß wrote:
> On 08.10.26 14:51, Konstantin Ryabitsev wrote:
> > THE REST matches every file in the tree via "F: *" and "F: */", so
> > get_maintainer.pl currently adds linux-kernel@vger.kernel.org to every
> > patch, regardless of whether the touched files already belong to a
> > subsystem with its own mailing list.
> >
> > Only add THE REST for a file when no other matching section provides a
> > mailing list for it. Files that match no section, or only sections
> > without an L: entry, still fall back to THE REST, so every patch keeps
> > reaching at least one public list.
> >
> > Signed-off-by: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
> > ---
> > LKML has become mostly a firehose of patches that are already going to a
> > subsystem list. The reason is THE REST: it matches every file in the
> > tree, so get_maintainer.pl adds linux-kernel@vger.kernel.org to every
> > single patch. During the week of Oct 1-7, 2026:
> >
> > - LKML carried 13,641 messages (~1,950/day), 90% of which were also
> > sent to at least one other list;
> > - with ~2,100 subscribers, that is about 29 million deliveries per
> > week for LKML alone.
> >
> > This issue came up during the 2026 Maintainer Summit and the consensus
> > was that "always include linux-kernel for every patch" was never the
> > intent.
> >
> > This patch makes THE REST a fallback as initially intended: it is only
> > added for a file when no other matching MAINTAINERS section provides a
> > mailing list for it.
>
> Hmm, for me this will be a major problem.
>
> As the Xen code maintainer I have stumbled over problematic patches which
> were NOT sent to x86 or xen ML several times, which made it possible to catch
> potential regressions early.
>
> Having to subscribe to each potentially interesting ML (or using korgalore on
> those) would not be my preferred workflow.
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.
Just my 2c,
Willy
next prev parent reply other threads:[~2026-10-09 18:37 UTC|newest]
Thread overview: 15+ 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-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 [this message]
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=ask0dkduRV5pxeLZ@1wt.eu \
--to=w@1wt.eu \
--cc=jgross@suse.com \
--cc=joe@perches.com \
--cc=konstantin@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=users@kernel.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
all inboxes | Powered by JetHome®