[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Ynxr6JNczWFTwxVw@mit.edu>
Date: Wed, 11 May 2022 22:07:36 -0400
From: "Theodore Ts'o" <tytso@....edu>
To: Konstantin Ryabitsev <konstantin@...uxfoundation.org>
Cc: Michael Ellerman <mpe@...erman.id.au>,
Linus Torvalds <torvalds@...ux-foundation.org>,
Nathan Chancellor <nathan@...nel.org>,
"Michael S. Tsirkin" <mst@...hat.com>,
KVM list <kvm@...r.kernel.org>,
virtualization@...ts.linux-foundation.org,
Netdev <netdev@...r.kernel.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
mie@...l.co.jp
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: https://lore.kernel.org/r/CAHk-=wgAk3NEJ2PHtb0jXzCUOGytiHLq=rzjkFKfpiuH-SROgA@mail.gmail.com
>
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