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  linux-cve-announce  PHC 
Open Source and information security mailing list archives
Hash Suite for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:   Wed, 11 May 2022 22:07:36 -0400
From:   "Theodore Ts'o" <>
To:     Konstantin Ryabitsev <>
Cc:     Michael Ellerman <>,
        Linus Torvalds <>,
        Nathan Chancellor <>,
        "Michael S. Tsirkin" <>,
        KVM list <>,,
        Netdev <>,
        Linux Kernel Mailing List <>,
Subject: Re: [GIT PULL] virtio: last minute fixup

On Wed, May 11, 2022 at 12:31:16PM -0400, Konstantin Ryabitsev wrote:
> > But my mailer, editor and terminal don't know what to do with a Message-Id.
> > 
> > Whereas they can all open an https link.
> > 
> > Making people paste message ids into lore to see the original submission
> > is not a win. People make enough fun of us already for still using email
> > to submit patches, let's not make their job any easier :)
> Okay, I'm fine with using a dedicated trailer for this purpose, perhaps an
> "Archived-At"? That's a real header that was proposed by IETF for similar
> purposes. E.g.:
>     Archived-at:

I'd suggest is "Patch-Link".  Then we can also have "Bug-Link:",
"Test-Link:", etc.

"Patch-Link" is a tad bit shorter "Archived-at", and ultimately, it's
not actually not the patch which is being archived.  It's the fact
that it's a pointer to the patch review which is of most interest.

					- Ted

Powered by blists - more mailing lists