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

Mark Brown
2024-06-14T14:43:29Z

[-- Attachment #1: Type: text/plain, Size: 1421 bytes --]

On Sat, Jun 15, 2024 at 12:29:09AM +1000, Michael Ellerman wrote:
> Konstantin Ryabitsev <konstantin@linuxfoundation.org> writes:

> > I suggest we move away from the practice of using Link: trailers to indicate
> > the patch provenance to using Message-Id: trailers for the same purpose. This
> > solves multiple problems:

> > 1. disambiguates Link: trailers so they point to relevant online discussions
> > 2. allows tooling like b4, patchwork, etc, to reliably match commits to
> > submissions for the purposes of better code review automation
> > 3. allows stable and similar projects to better track series grouping for
> > commits

> Message-Id: sucks, I want a link I can open with a single click.

> At your suggestion I switched to using https://msgid.link/ as the target
> for patch links, eg:

> Link: https://msgid.link/20240529123029.146953-2-mpe@ellerman.id.au

> Which gives the reader a hint that the link is just to the submission.

> I don't really care if the tag is "Link:", but it has to be a URL, not
> just a bare message-id that I have to cut and paste like it's the stone
> age.

Actually now that you mention it some terminals (GNOME I think?) have a
feature where they'll identify strings with an @ in them as e-mail
addresses and if you click on one they'll try to fire up some GUI mail
client with a new e-mail addressed to that. This interacts poorly with
using message IDs a lot.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]