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

Takashi Iwai
2024-06-16T11:39:08Z

On Sun, 16 Jun 2024 10:10:25 +0200,
Paolo Bonzini wrote:
>
> On 6/16/24 03:13, Linus Torvalds wrote:
> > And no, I'm not at all happy with the fact that apparently vhost and
> > kvm has made it their thing.
> >
> > Paolo, Michael, Takashi, please put useful links, not those braindead
> > message id's in your commit messages.
>
> Ok, ok. Before lore existed, there was no service that I can remember
> that archived messages with a message-id in the URL. So, for example
> Gmane links would be useless now, and patchwork links are not really
> something I'd trust for long-term archival either.
>
> These days, it's mostly just that I have set am.message-id to true
> years ago; but since lore is managed by kernel.org, we can expect the
> URLs to be stable and the original reason to use Message-ID is
> obsolete. Having learnt right now about the applypatch-msg git hook,
> I've stuck a
>
> sed -i -e 's,^Message-ID: <\(.*\)>$,Link:
> https://lore.kernel.org/r/\1,' "$1"
>
> in there which should do the trick. I guess Michael and Takashi can
> do the same. :)

Heh, that's actually what I've done already, but my script had
"Message-Id" or such to match and it didn't hit any longer after some
mail change; as a result, Message-id tag remained. You'd better to
make it case-insensitive match.

HTH,

Takashi