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

Paul E. McKenney
2024-06-17T16:04:16Z

On Mon, Jun 17, 2024 at 10:39:14AM -0400, Konstantin Ryabitsev wrote:

[ . . .]

> I understand the reasons why everyone hates having the "Message-ID:" trailer,
> and this is fine. Can I counter-propose that we have a unique URL for links
> specifically going to patch submissions from which the commits were made? I've
> been already recommending using the "msgid.link" domain, but I'll go a bit
> further and put forward the recommendation that:
>
> - commits MAY have Link: trailers indicating the exact origin of the patch. To
> distinguish these links from other Link: trailers that may lead to relevant
> online discussions, they should either use the "patch.msgid.link" domain, or
> indicate the nature of the link using the hash-notation. Examples:
>
> - Link: https://patch.msgid.link/message@id-here
> - Link: https://lore.kernel.org/message@id-here # patch

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

Or am I confusing keywords with variables in your canonical URLs?

If so, could you please post an example?

Thanx, Paul