lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  PHC 
Open Source and information security mailing list archives
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:   Thu, 12 May 2022 23:30:15 +1000
From:   Michael Ellerman <>
To:     Linus Torvalds <>
Cc:     "Michael S. Tsirkin" <>,
        Konstantin Ryabitsev <>,
        KVM list <>,,
        Netdev <>,
        Linux Kernel Mailing List <>,
Subject: Re: [GIT PULL] virtio: last minute fixup

Linus Torvalds <> writes:
> On Wed, May 11, 2022 at 3:12 AM Michael Ellerman <> wrote:
>> Which I read as you endorsing Link: tags :)
> I absolutely adore "Link:" tags. They've been great.
> But they've been great for links that are *usedful*.
> They are wonderful when they link to the original problem.
> They are *really* wonderful when they link to some long discussion
> about how to solve the problem.
> They are completely useless when they link to "this is the patch
> submission of the SAME DAMN PATCH THAT THE COMMIT IS".

Folks wanted to add Change-Id: tags to every commit.

You said we didn't need to, because we have the Link: to the original
patch submission, which includes the Message-Id and therefore is a
de facto change id.

Links to other random places don't serve that function.


Powered by blists - more mailing lists