All of lore.kernel.org
 help / color / mirror / Atom feed
From: Willy Tarreau <w@1wt.eu>
To: Christoph Hellwig <hch@infradead.org>
Cc: "Eric W. Biederman" <ebiederm@xmission.com>,
	Konstantin Ryabitsev <konstantin@linuxfoundation.org>,
	users@linux.kernel.org, ksummit@lists.linux.dev
Subject: Re: RFC: switching "THE REST" in MAINTAINERS away from linux-kernel@vger.kernel.org
Date: Tue, 7 Nov 2023 05:04:33 +0100	[thread overview]
Message-ID: <20231107040433.GA23816@1wt.eu> (raw)
In-Reply-To: <ZUkcyCb5DEVEDkKj@infradead.org>

On Mon, Nov 06, 2023 at 09:05:12AM -0800, Christoph Hellwig wrote:
> On Mon, Nov 06, 2023 at 10:11:48AM -0600, Eric W. Biederman wrote:
> > > - due to the sheer volume of messages, LKML is generally seen as useless for
> > >   holding any actual discussions
> > 
> > I have never had that impression of LKML.
> 
> Same here, I am actually reading through lkml, although superficially
> skipping over some bits, and definitively starting discussions there.

Same here. I used to have a procmail filter to deliver lkml to its own
box a decade ago and I figured that I lost contact with what was happening
so I removed that filter so that I move all these messages manually several
times a day after scrolling over them (a single key in mutt). This way
every day I can have a quick glance at all subjects there, that's how I
discover new topics, patch series, discussions etc. I think that a non
negligible number of LKML subscribers are there for this exact reason.

I would personally miss these messages if they would not be delivered
there anymore :-/ And I don't think that the situation would significantly
improve in the short term anyway due to this.

> Restricting access to the new lkml is not acceptable.  How about
> restricting access to all lists for gmail addresses if gmail is so
> broken?

Or even simpler, flush the queue very often and make it clear that gmail
is not a reliable recipiet for LKML. The trouble will self-regulate.

Just my two cents,
Willy

  parent reply	other threads:[~2023-11-07  4:19 UTC|newest]

Thread overview: 71+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-06 15:33 RFC: switching "THE REST" in MAINTAINERS away from linux-kernel@vger.kernel.org Konstantin Ryabitsev
2023-11-06 15:43 ` Joe Perches
2023-11-06 15:52 ` Borislav Petkov
2023-11-06 16:05 ` [workflows]RFC: " Steven Rostedt
2023-11-06 16:29   ` Miquel Raynal
2023-11-06 17:45     ` Konstantin Ryabitsev
2023-11-08 16:19   ` Joe Perches
2023-11-08 16:44     ` Mark Brown
2023-11-08 18:16       ` Joe Perches
2023-11-08 19:04         ` Steven Rostedt
2023-11-08 19:14           ` Joe Perches
2023-11-08 19:34             ` Steven Rostedt
2023-11-08 20:07               ` [workflows]Re: " Steven Rostedt
2023-11-08 20:14                 ` Joe Perches
2023-11-08 20:36                   ` Joe Perches
2023-11-08 20:49                     ` Joe Perches
2023-11-08 20:56                       ` Steven Rostedt
2023-11-08 21:04                         ` Konstantin Ryabitsev
2023-11-08 21:11                           ` Steven Rostedt
2023-11-08 20:41                 ` Joe Perches
2023-11-09 11:21               ` Mark Brown
2023-11-09 11:29                 ` Laurent Pinchart
2023-11-09  8:32           ` Dan Carpenter
2023-11-09  9:27             ` Laurent Pinchart
2023-11-09 17:14               ` Alex Elder
2023-11-09 17:25                 ` Konstantin Ryabitsev
2023-11-09 19:11                   ` Joe Perches
2023-11-09 19:38                     ` Konstantin Ryabitsev
2023-11-09 23:16                       ` Jason Gunthorpe
2023-11-10  0:56                         ` Linus Torvalds
2023-11-10 17:04                           ` Jakub Kicinski
2023-11-10 17:24                             ` Konstantin Ryabitsev
2023-11-10 17:55                               ` Jakub Kicinski
2023-11-10 17:24                             ` Rob Herring
2023-11-10 18:04                               ` Jakub Kicinski
2023-11-09 15:51             ` Steven Rostedt
2023-11-09 16:08               ` Laurent Pinchart
2023-11-09 16:16                 ` Steven Rostedt
2023-11-06 16:11 ` RFC: " Eric W. Biederman
2023-11-06 17:05   ` Christoph Hellwig
2023-11-06 17:41     ` Konstantin Ryabitsev
2023-11-09  3:55       ` Ian Kelling
2023-11-11 16:57       ` Theodore Ts'o
2023-11-07  4:04     ` Willy Tarreau [this message]
2023-11-06 17:21   ` Eric Wong
2023-11-06 17:56     ` Eric W. Biederman
2023-11-09 14:24   ` Naveen N Rao
2023-11-06 17:23 ` Richard Weinberger
2023-11-06 20:52   ` Randy Dunlap
2023-11-06 21:37 ` Jakub Kicinski
2023-11-06 22:52 ` Pavel Machek
2023-11-07  9:18   ` Paolo Bonzini
2023-11-07 10:15     ` Laurent Pinchart
2023-11-07 10:42       ` Greg KH
2023-11-07 12:14       ` Pratyush Yadav
2023-11-07 12:47         ` Julia Lawall
2023-11-07 13:18           ` Dan Carpenter
2023-11-07 13:23           ` Pratyush Yadav
2023-11-07 16:35           ` Konstantin Ryabitsev
2023-11-07 16:43             ` Paolo Bonzini
2023-11-07 16:51               ` Konstantin Ryabitsev
2023-11-10 10:01                 ` Paolo Bonzini
2023-11-07 10:47     ` Mark Brown
2023-11-07 13:24 ` Dan Carpenter
2023-11-08 20:04 ` Bird, Tim
2023-11-08 21:03   ` Luck, Tony
2023-11-08 21:04   ` James Bottomley
2023-11-08 21:18     ` Johannes Berg
2023-11-08 21:30     ` Rob Herring
2023-11-21 14:53 ` Joe Perches
2023-11-21 18:08   ` Greg KH

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=20231107040433.GA23816@1wt.eu \
    --to=w@1wt.eu \
    --cc=ebiederm@xmission.com \
    --cc=hch@infradead.org \
    --cc=konstantin@linuxfoundation.org \
    --cc=ksummit@lists.linux.dev \
    --cc=users@linux.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 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.