linux-kernel - Re: [PATCH] get_maintainer: only show lkml as last resort

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <19a701a8d5837088aa7d8ba594c228c0e040e747.camel@perches.com>
Date:   Tue, 06 Jul 2021 09:00:42 -0700
From:   Joe Perches <joe@...ches.com>
To:     Hannu Hartikainen <hannu@...k.in>, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] get_maintainer: only show lkml as last resort

On Tue, 2021-07-06 at 11:33 +0300, Hannu Hartikainen wrote:
> The documentation implies that patches should be primarily sent to a
> subsystem-specific mailing list [0]. Make get_maintainer only return the
> generic linux-kernel@...r.kernel.org ("THE REST") list when no other
> matching mailing list is found.
> 
> Most patches sent to lkml today are also sent to some other list. This
> change should lower the message volume on lkml in the long run, making
> the list more useful for those cases where it's the only option.
> 
> [0]: Documentation/process/submitting-patches.rst:
> > You should also normally choose at least one mailing list to receive a
> > copy of your patch set. linux-kernel@...r.kernel.org functions as a
> > list of last resort, but the volume on that list has caused a number of
> > developers to tune it out. Look in the MAINTAINERS file for a
> > subsystem-specific list; your patch will probably get more attention
> > there.
> 
> Signed-off-by: Hannu Hartikainen <hannu@...k.in>
> ---
> 
> I'm not sure if this is technically the best solution so I'm looking
> forward to review comments. But process-wise I think this should be a
> good change.

Almost no one reads lkml directly anyway and I rather like that lkml
gets all copies.

This allows lore.kernel.org/lkml to have a relatively complete searchable
database of all kernel related patch submissions.

Another solution might be an searchable aggregation mechanism at lore,
but I believe one currently does not exist.

That _might_ allow a similar search mechanism.

> diff --git a/scripts/get_maintainer.pl b/scripts/get_maintainer.pl

The proposed patch seems overly complicated.