Re: [workflows]RFC: switching "THE REST" in MAINTAINERS away from linux-kernel@vger.kernel.org

Konstantin Ryabitsev
2023-11-09T19:38:59Z

On Thu, Nov 09, 2023 at 11:11:08AM -0800, Joe Perches wrote:
> > > My input is that whatever the outcome of all this discussion, please
> > > define it as policy and have get_maintainer.pl implement it. I don't
> > > want to have to think too hard about who *should* be included (beyond
> > > people I already know).
> >
> > Yes, I fully agree with you -- people shouldn't need to know where the patches
> > should be going. The tooling should decide this for them, and I want to change
> > the tooling so that it no longer includes linux-kernel@vger on everything,
> > only on patches without any other mailing list matches.
>
> Relatively easy to do, but what about your original request/suggestion
> to use patches@lists.linux.dev ?

Happy to go that route, just need to get the buy-in from everyone, which I
intend to bring up at the maintainers summit. My proposed course of action
is:

1. Update get_maintainer.pl so that linux-kernel@vger.kernel.org is no longer
added on "THE REST" fall-through, unless there are no other L: entries that
matched.
2. Add functionality to public-inbox to provide RSS feeds for "new topics" and
"hot topics" that would allow following individual lists and the /all/
aggregator. This is under discussion on the public-inbox meta list [1], so
there is no final decision on this being included.
3. Figure out the best way to specify the "always-cc" address that should be
always included by get_maintainer, either via MAINTAINERS, or via some kind
of dot-file. Maybe just have this in MAINTAINERS:

ALWAYS CC
L: patches@lists.linux.dev

And have special treatment for that entry.

I think this should gradually improve the linux-kernel mailing list to the
point where most people will start reading it again.

-K

[1] https://public-inbox.org/meta/20231107-skilled-cobra-of-swiftness-a6ff26@meerkat/T/#t