Re: [PATCH v2 0/2] get_maintainer: stop sending every patch to LKML

[David Laight <david.laight.linux@gmail.com>]

On Mon, 2 Nov 2026 12:56:28 -0500
Konstantin Ryabitsev <konstantin@linuxfoundation.org> wrote:

> On Mon, Nov 02, 2026 at 05:24:51PM +0100, Geert Uytterhoeven wrote:
> > > I certainly scan it.
> > > It is also useful to have an archived local copy that can be searched.  
> > 
> > Indeed. Sorry to say that, but Gmail web interface search is still
> > much more effective than lore web interface search.  
> 
> Folks, I don't want this to turn into another thread of "me too" responses.
> 
> Yes, I know that some people still use it for a number of legitimate reasons
> -- but these are few-and-far-between exceptions. I need this change because
> the current status quo is NOT TENABLE. *Everyone's* quality of life is
> affected because Gmail's throttling results in (looks) ~350,000 mails in the
> queue, most of them waiting for Google to graciously allow us to talk to them.

They are actually waiting for gmail to reject them so often they get deleted.
If you try subscribing a gmail address to lkml it really doesn't work very well.
Maybe you get 70% of the emails (hard to say) but they all arrive out of order
and sometimes days late - makes a real mess of patch sets.

More interesting would be not sending any patch emails (and replies to) to
gmail addresses.
That isn't as harsh as unsubscribing gmail addresses and still leaves the
gmail addresses getting any 'admin' messages.

> 
> So, we either unsubscribe all gmail addresses from LKML and prevent them from
> resubscribing, or we do something less drastic and revert it to how it was
> supposed to work in the first place -- only patches without a dedicated list
> end up on LKML.

Then those of us who want to see most emails (or use local filters) will have
to subscribe to all the lists we can think of, and then handle the fact that
we receive multiple copies of emails that get sent to multiple lists.

David

> 
> -K