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

[Paolo Bonzini <pbonzini@redhat.com>]

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. :)


By the way, if you use Firefox, you can do the following two steps to 
install a search plugin that searches lore by Message-ID:

- first go to 
https://mycroftproject.com/install.html?id=121759&basename=lore_kernel_org&icontype=png&name=lore.kernel.org 
to install the search engine (an XML file, you can see it at 
https://mycroftproject.com/installos.php/121759/lore_kernel_org.xml).

- then go to about:preferences#search and add a search shortcut

On Chrome instead you can add https://lore.kernel.org/r/%s at 
chrome://settings/searchEngines.

(Apart from git commit messages, I use it also with the 
https://addons.thunderbird.net/en-us/thunderbird/addon/copy-message-id/ 
extension for Thunderbird).

Paolo