mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
To: "Jason A. Donenfeld" <Jason@zx2c4.com>
Cc: Joe Perches <joe@perches.com>,
	linux-kernel@vger.kernel.org,  users@kernel.org
Subject: Re: [PATCH] get_maintainer: only use THE REST as a fallback
Date: Thu, 8 Oct 2026 09:10:18 -0400	[thread overview]
Message-ID: <20261008-quiet-lucky-ferret-3498cb@lemur> (raw)
In-Reply-To: <CAHmME9rh7k0vNrBt4yF7fOgir3yuhrFawPnmsJpeYBCLg-r6bA@mail.gmail.com>

On Thu, Oct 08, 2026 at 03:03:11PM +0200, Jason A. Donenfeld wrote:
> On Thu, Oct 8, 2026 at 2:56 PM Konstantin Ryabitsev
> <konstantin@linuxfoundation.org> wrote:
> > This issue came up during the 2026 Maintainer Summit and the consensus
> > was that "always include linux-kernel for every patch" was never the
> > intent.
> 
> Thanks for communicating this! I had always assumed the opposite,
> based on what I saw happening. Glad it's been settled.

Note, that if we DO want to send all patches to a dedicated mailing list, this
can be accommodated, too -- just not the list with 2100 subscribers (because
it's not working). We have patches@lists.linux.dev, which was originally set
up as an archive-only dumping ground with no subscribers (by design).

If considered useful, I can update this patch to get us both worlds:

- THE REST actually works as a fallback
- patches@lists.linux.dev is included on all patches as an archival list

-K

  reply	other threads:[~2026-10-08 13:10 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-08 12:51 Konstantin Ryabitsev
2026-10-08 13:03 ` Jason A. Donenfeld
2026-10-08 13:10   ` Konstantin Ryabitsev [this message]
2026-10-08 13:22     ` Matthieu Baerts
2026-10-08 14:05       ` Konstantin Ryabitsev
2026-10-08 16:04         ` Matthieu Baerts
2026-10-09 16:41     ` Jason A. Donenfeld
2026-10-09 22:25       ` Konstantin Ryabitsev
2026-10-08 13:15 ` Jürgen Groß
2026-10-08 14:02   ` Konstantin Ryabitsev
2026-10-09 12:24   ` Jason Gunthorpe
2026-10-09 18:37   ` Willy Tarreau
2026-10-11  1:21     ` [workflows]Re: " Steven Rostedt
2026-10-09 23:35   ` Michael Kelley
2026-10-08 13:15 ` Michael S. Tsirkin
2026-10-08 13:39 ` Petr Pavlu
2026-10-08 14:06   ` Konstantin Ryabitsev
2026-10-09 16:25 ` Joe Perches

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=20261008-quiet-lucky-ferret-3498cb@lemur \
    --to=konstantin@linuxfoundation.org \
    --cc=Jason@zx2c4.com \
    --cc=joe@perches.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=users@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®