Re: [MAINTAINERS SUMMIT] [4/4] Discuss how to better prevent backports of commits that turn out to cause regressions

Paolo Bonzini
2024-06-17T16:14:53Z

On 6/17/24 18:06, Konstantin Ryabitsev wrote:
> On Mon, Jun 17, 2024 at 09:04:15AM GMT, Paul E. McKenney wrote:
>> So for your message that I am replying to, this would be like these?
>>
>> - Link: https://patch.msgid.link/message@20240617-arboreal-industrious-hedgehog-5b84ae@meerkat
>> - Link: https://lore.kernel.org/message@20240617-arboreal-industrious-hedgehog-5b84ae@meerkat # patch
>
> The "message@id-here" means the entire message-id:
>
> - Link: https://patch.msgid.link/20240617-arboreal-industrious-hedgehog-5b84ae@meerkat
> - Link: https://lore.kernel.org/20240617-arboreal-industrious-hedgehog-5b84ae@meerkat # patch

Two questions:

1) just one is needed, right? (should go without saying, but still)

2) Is the "/r/MESSAGE-ID" format
(https://lore.kernel.org/r/20240617-arboreal-industrious-hedgehog-5b84ae@meerkat)
not valid or deprecated?

And of course, to Linus's point from yesterday, this would only apply to
patches that _did_ come from a mailing list that is indexed by lore.

Paolo