Konstantin Ryabitsev <[email protected]> writes: ... > > I think we should simply disambiguate the trailer added by tooling like b4. > Instead of using Link:, it can go back to using Message-Id, which is already > standard with git -- it's trivial for git.kernel.org to link them to > lore.kernel.org.
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 :) > Before: > > Signed-off-by: Main Tainer <[email protected]> > Link: > https://lore.kernel.org/r/CAHk-=wgAk3NEJ2PHtb0jXzCUOGytiHLq=rzjkfkfpiuh-sr...@mail.gmail.com > > After: > > Signed-off-by: Main Tainer <[email protected]> > Message-Id: > <CAHk-=wgAk3NEJ2PHtb0jXzCUOGytiHLq=rzjkfkfpiuh-sr...@mail.gmail.com> > > This would allow people to still use Link: for things like linking to actual > ML discussions. I know this pollutes commits a bit, but I would argue that > this is a worthwhile trade-off that allows us to improve our automation and > better scale maintainers. I went back through the history and I'm pretty sure that the original use for "Link:" was to link to the original submission, done by tip-bot starting back in 2011: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=f994d99cf140dbb637e49882891c89b3fd84becd Prior to that there were no "Link:" tags, only "BugLink:". But if people want to reclaim "Link:" for generic links then fine, but let's still use a https link, just give it a different name. eg. "PatchLink:", or "Submitted:" etc. cheers _______________________________________________ Virtualization mailing list [email protected] https://lists.linuxfoundation.org/mailman/listinfo/virtualization
