mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
To: Matthieu Baerts <matttbe@kernel.org>
Cc: "Jason A. Donenfeld" <Jason@zx2c4.com>,
	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 10:05:15 -0400	[thread overview]
Message-ID: <20261008-quantum-polar-kraken-890dac@lemur> (raw)
In-Reply-To: <e1f160bb-adef-49e0-acb6-628b259b7975@kernel.org>

On Thu, Oct 08, 2026 at 03:22:56PM +0200, Matthieu Baerts wrote:
> Is this list actively being used? The risk I see with this list is
> having someone sending a new version of an existing patch only to this
> list: this version will then be picked by tools like b4. If the
> maintainer doesn't pay attention to the info messages, a wrong version
> might be applied instead. Maybe b4 should catch such patches?

I'm trying to think of how this would happen. If the submitter users
get-maintainer.pl, then they should always get the correct set of lists. If
they aren't using get-maintainer.pl, then they aren't really likely to use
just the patches archive list.

If they use b4 to send the patches, then even if they do manage to mess up the
recipients, somehow, the maintainer should still be able to find it via the
change-id search.

-K

  reply	other threads:[~2026-10-08 14:05 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
2026-10-08 13:22     ` Matthieu Baerts
2026-10-08 14:05       ` Konstantin Ryabitsev [this message]
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-quantum-polar-kraken-890dac@lemur \
    --to=konstantin@linuxfoundation.org \
    --cc=Jason@zx2c4.com \
    --cc=joe@perches.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=matttbe@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®