From: David Laight <david.laight.linux@gmail.com>
To: Jonathan Corbet <corbet@lwn.net>
Cc: "Rafael J. Wysocki (Intel)" <rafael@kernel.org>,
Konstantin Ryabitsev <konstantin@linuxfoundation.org>,
Joe Perches <joe@perches.com>,
Shuah Khan <skhan@linuxfoundation.org>,
Randy Dunlap <rdunlap@infradead.org>,
linux-kernel@vger.kernel.org, users@kernel.org,
Federico Vaga <federico.vaga@vaga.pv.it>,
Akira Yokosawa <akiyks@gmail.com>,
Carlos Bilbao <carlos.bilbao@kernel.org>,
Avadhut Naik <avadhut.naik@amd.com>, Alex Shi <alexs@kernel.org>,
Yanteng Si <si.yanteng@linux.dev>,
Dongliang Mu <dzm91@hust.edu.cn>,
Chen-Yu Yeh <chenyou910331@gmail.com>, Weijie Yuan <wy@wyuan.org>,
workflows@vger.kernel.org, linux-doc@vger.kernel.org,
Petr Pavlu <petr.pavlu@suse.com>
Subject: Re: [PATCH v2 0/2] get_maintainer: stop sending every patch to LKML
Date: Mon, 2 Nov 2026 15:05:35 +0000 [thread overview]
Message-ID: <20261102150535.6c5689f6@pumpkin> (raw)
In-Reply-To: <87a4nrfgjm.fsf@trenco.lwn.net>
On Mon, 02 Nov 2026 07:34:37 -0700
Jonathan Corbet <corbet@lwn.net> wrote:
> "Rafael J. Wysocki (Intel)" <rafael@kernel.org> writes:
>
> > So it occurred to me that it might be actually better to stop sending
> > messages directly to LKML subscribers and only make it available for
> > download somewhere and as a Lore archive.
> >
> > Is there really anyone depending on receiving all of the LKML traffic every day?
>
> * raises hand
>
> Some of us crazy people really do depend on it, yes.
I certainly scan it.
It is also useful to have an archived local copy that can be searched.
I can see a point in not copying all of netdev to lkml, but there is
little point not copying patches to low-volume lists.
David
>
> jon
next prev parent reply other threads:[~2026-11-02 15:05 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-20 15:35 [PATCH v2 0/2] get_maintainer: stop sending every patch to LKML Konstantin Ryabitsev
2026-10-20 15:35 ` [PATCH v2 1/2] get_maintainer: only use THE REST as a fallback Konstantin Ryabitsev
2026-10-20 15:47 ` Joe Perches
2026-10-20 15:52 ` Konstantin Ryabitsev
2026-10-20 16:39 ` Joe Perches
2026-10-20 15:35 ` [PATCH v2 2/2] docs: submitting-patches: make LKML a list of last resort again Konstantin Ryabitsev
2026-10-20 16:58 ` Randy Dunlap
2026-10-21 6:29 ` Krzysztof Kozlowski
2026-10-21 6:48 ` Greg KH
2026-10-21 8:33 ` Lee Jones
2026-10-21 20:33 ` Jiri Kosina
2026-10-20 15:53 ` [PATCH v2 0/2] get_maintainer: stop sending every patch to LKML Joe Perches
2026-10-20 18:51 ` Theodore Tso
2026-10-21 9:13 ` Geert Uytterhoeven
2026-10-20 16:44 ` Weijie Yuan
2026-11-01 14:42 ` Konstantin Ryabitsev
2026-11-02 9:32 ` David Laight
2026-11-02 14:12 ` Konstantin Ryabitsev
2026-11-02 14:18 ` Rafael J. Wysocki (Intel)
2026-11-02 14:34 ` Jonathan Corbet
2026-11-02 14:45 ` Rafael J. Wysocki (Intel)
2026-11-02 17:15 ` Sean Christopherson
2026-11-02 15:05 ` David Laight [this message]
2026-11-02 15:47 ` Jonathan Corbet
2026-11-02 16:10 ` Joe Perches
2026-11-02 16:23 ` Konstantin Ryabitsev
2026-11-02 16:20 ` Konstantin Ryabitsev
2026-11-02 16:24 ` Geert Uytterhoeven
2026-11-02 17:17 ` David Laight
2026-11-02 17:56 ` Konstantin Ryabitsev
2026-11-02 18:25 ` Rafael J. Wysocki (Intel)
2026-11-02 19:31 ` David Laight
2026-11-03 0:16 ` Dongliang Mu
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=20261102150535.6c5689f6@pumpkin \
--to=david.laight.linux@gmail.com \
--cc=akiyks@gmail.com \
--cc=alexs@kernel.org \
--cc=avadhut.naik@amd.com \
--cc=carlos.bilbao@kernel.org \
--cc=chenyou910331@gmail.com \
--cc=corbet@lwn.net \
--cc=dzm91@hust.edu.cn \
--cc=federico.vaga@vaga.pv.it \
--cc=joe@perches.com \
--cc=konstantin@linuxfoundation.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=petr.pavlu@suse.com \
--cc=rafael@kernel.org \
--cc=rdunlap@infradead.org \
--cc=si.yanteng@linux.dev \
--cc=skhan@linuxfoundation.org \
--cc=users@kernel.org \
--cc=workflows@vger.kernel.org \
--cc=wy@wyuan.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.