From: Pratyush Yadav <pratyush@kernel.org>
To: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Cc: Paolo Bonzini <pbonzini@redhat.com>, Pavel Machek <pavel@ucw.cz>,
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, 07 Nov 2023 13:14:01 +0100 [thread overview]
Message-ID: <mafs0o7g5hiba.fsf_-_@kernel.org> (raw)
In-Reply-To: <20231107101513.GB27932@pendragon.ideasonboard.com> (Laurent Pinchart's message of "Tue, 7 Nov 2023 12:15:13 +0200")
On Tue, Nov 07 2023, Laurent Pinchart wrote:
> On Tue, Nov 07, 2023 at 10:18:58AM +0100, Paolo Bonzini wrote:
>> On 11/6/23 23:52, Pavel Machek wrote:
>> >> For this reason, I propose switching the "F: *" entry in MAINTAINERS
>> >> ("THE REST") topatches@lists.linux.dev instead. This list differs from LKML
>> >> in the following important aspects:
>> >
>> > How many patches are in "the rest" area? I don't think it is that
>> > many, and I believe those should be broadcasted, as it is not clear
>> > who should handle them. And lkml seems to be reasonable place for them
>> > at the moment.
>>
>> Indeed, I suspect that a lot of the traffic to LKML does not come from
>> "THE REST", but rather from people using a git-send-email configuration like
>>
>> [sendemail]
>> to = linux-kernel@vger.kernel.org
FWIW, I do not have this nor have I seen any of my colleagues ever have
this in their config. In the patches I send, lkml always comes from
get_maintainers.pl.
>
> Do we document this as being a recommended git-send-email configuration
> ? That sounds horrible :-( Documentation/process/submitting-patches.rst
> states
>
> linux-kernel@vger.kernel.org should be used by default for all
> patches, but the volume on that list has caused a number of developers
> to tune it out. Please do not spam unrelated lists and unrelated
> people, though.
>
> This should be updated, even if for the only reason that the text is
> quite confusing (in my opinion at least, I'm not sure if it means LKML
> should be used for all patches, or shouldn't).
>
> To give another data point, balancing a bit the replies that expressed
> surprise at Konstantin's point that LKML is generally seen as useless
> for holding actual discussions, I do not follow LKML at all due to the
> amount of mails that are not general discussions. It drowns the useful
> information in noise for me.
Yes, same for me. In general, I find the mail volume on LKML to be too
large for me to subscribe to it. Of late I have been relying more and
more on public-inbox and lei to read and browse kernel mail.
--
Regards,
Pratyush Yadav
next prev parent reply other threads:[~2023-11-07 12:14 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
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 [this message]
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=mafs0o7g5hiba.fsf_-_@kernel.org \
--to=pratyush@kernel.org \
--cc=konstantin@linuxfoundation.org \
--cc=ksummit@lists.linux.dev \
--cc=laurent.pinchart@ideasonboard.com \
--cc=pavel@ucw.cz \
--cc=pbonzini@redhat.com \
--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.