From: Joe Perches <joe@perches.com>
To: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
Cc: Jonathan Corbet <corbet@lwn.net>,
Shuah Khan <skhan@linuxfoundation.org>,
Randy Dunlap <rdunlap@infradead.org>,
linux-kernel@vger.kernel.org, users@kernel.org,
Federico Vaga <federico.vaga@vaga.pv.it>,
Akira Yokosawa <akiyks@gmail.com>,
Carlos Bilbao <carlos.bilbao@kernel.org>,
Avadhut Naik <avadhut.naik@amd.com>, Alex Shi <alexs@kernel.org>,
Yanteng Si <si.yanteng@linux.dev>,
Dongliang Mu <dzm91@hust.edu.cn>,
Chen-Yu Yeh <chenyou910331@gmail.com>, Weijie Yuan <wy@wyuan.org>,
workflows@vger.kernel.org, linux-doc@vger.kernel.org
Subject: Re: [PATCH v2 1/2] get_maintainer: only use THE REST as a fallback
Date: Tue, 20 Oct 2026 09:39:46 -0700 [thread overview]
Message-ID: <23b3cedc62f21179d9374661dc3dad06@perches.com> (raw)
In-Reply-To: <20261020-witty-proud-coot-89ecd3@lemur>
On 2026-10-20 08:52, Konstantin Ryabitsev wrote:
> On Tue, Oct 20, 2026 at 08:47:01AM -0700, Joe Perches wrote:
>> > Only add THE REST for a file when no other matching section provides a
>> > mailing list that get_maintainer.pl would actually output. Lists marked
>> > "subscribers-only" are omitted unless --s is given, and lists marked
>> > "moderated" are omitted with --no-moderated, so such lists don't count
>> > as a destination in those cases. Files that match no section, or only
>> > sections without such a list, still fall back to THE REST, so every
>> > patch keeps reaching at least one known-public mailing list.
>> >
>> > Signed-off-by: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
>> > ---
>>
>> I don't disagree that this is useful but v2: no changelog
>>
>> Perhaps there's a simpler and more generic mechanism. I'll play with
>> it for
>> a couple days.
>
> It's like to convey the sense of urgency -- with the amount of patches,
> automated reviews, and follow-ups being sent daily, having all of them
> land on
> LKML and delivered to 2000+ subscribers... is not sustainable. At this
> point,
> I'm very close to outright banning subscriptions from gmail, outlook
> and yahoo
> addresses. Not sending every single patch to the LKML is a better way
> to deal
> with this.
No worries.
Apply it and I might deal with later.
next prev parent reply other threads:[~2026-10-20 16:39 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-20 15:35 [PATCH v2 0/2] get_maintainer: stop sending every patch to LKML Konstantin Ryabitsev
2026-10-20 15:35 ` [PATCH v2 1/2] get_maintainer: only use THE REST as a fallback Konstantin Ryabitsev
2026-10-20 15:47 ` Joe Perches
2026-10-20 15:52 ` Konstantin Ryabitsev
2026-10-20 16:39 ` Joe Perches [this message]
2026-10-20 15:35 ` [PATCH v2 2/2] docs: submitting-patches: make LKML a list of last resort again Konstantin Ryabitsev
2026-10-20 16:58 ` Randy Dunlap
2026-10-20 15:53 ` [PATCH v2 0/2] get_maintainer: stop sending every patch to LKML Joe Perches
2026-10-20 18:51 ` Theodore Tso
2026-10-20 16:44 ` Weijie Yuan
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=23b3cedc62f21179d9374661dc3dad06@perches.com \
--to=joe@perches.com \
--cc=akiyks@gmail.com \
--cc=alexs@kernel.org \
--cc=avadhut.naik@amd.com \
--cc=carlos.bilbao@kernel.org \
--cc=chenyou910331@gmail.com \
--cc=corbet@lwn.net \
--cc=dzm91@hust.edu.cn \
--cc=federico.vaga@vaga.pv.it \
--cc=konstantin@linuxfoundation.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rdunlap@infradead.org \
--cc=si.yanteng@linux.dev \
--cc=skhan@linuxfoundation.org \
--cc=users@kernel.org \
--cc=workflows@vger.kernel.org \
--cc=wy@wyuan.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.