Re: [PATCH] get_maintainer: only use THE REST as a fallback

[Matthieu Baerts]

On 08/10/2026 16:05, Konstantin Ryabitsev wrote:
> 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.

Sorry, I meant to say: when someone is trying to discretely get a bad
version applied on purpose. For example: user A sends a v1 using
get_maintainer.pl, then user B (or A) could send a v2 (or a v1 with
other content) only to patches@xxxxxxxxxxxxxxx. In this case, a
maintainer who wants to apply the original v1, might end-up applying the
"bad" and "hidden" patch.

Or maybe "b4" already prevents that or is clear enough when picking a
newer/different version than the given one?

Cheers,
Matt
-- 
Sponsored by the NGI0 Core fund.