Re: [Ksummit-discuss] [MAINTAINERS SUMMIT] Patch version changes in commit logs?

[Dan Carpenter <dan.carpenter@oracle.com>]

On Mon, Jul 01, 2019 at 09:53:54AM +0200, Takashi Iwai wrote:
> On Mon, 01 Jul 2019 09:49:56 +0200,
> Thomas Gleixner wrote:
> > 
> > On Mon, 1 Jul 2019, Peter Zijlstra wrote:
> > 
> > > On Sun, Jun 30, 2019 at 12:31:20PM -0400, Konstantin Ryabitsev wrote:
> > > > On Sat, Jun 29, 2019 at 05:16:18PM +0200, Thomas Gleixner wrote:
> > > > > > Makes all sense to me.  One question/remark:
> > > > > > 
> > > > > > Documentation/process/submitting-patches.rst says:
> > > > > > 
> > > > > >  "If the patch follows from a mailing list discussion, give a URL to the
> > > > > >   mailing list archive; use the https://lkml.kernel.org/ redirector with
> > > > > >   a ``Message-Id``, to ensure that the links cannot become stale."
> > > > > > 
> > > > > > and it does not mention "lore.kernel.org": does this doc want an update?
> > > > > 
> > > > > Yes. lkml.kernel.org/r was the initial redirector, but lore is the new
> > > > > thing.
> > > > 
> > > > FYI, lkml.kernel.org == lore.kernel.org in all respects. Using
> > > > lore.kernel.org/r/<messageid> will match *any* mailing list archived at
> > > > lore.kernel.org (for the full list, see https://lore.kernel.org/lists.html).
> > > > I prefer people use lore.kernel.org because that name doesn't imply that the
> > > > search will only match LKML.
> > > 
> > > I much prefer https://lkml.kernel.org/r/$msgid over lore, because I can
> > > change it to marc.info with a single character change. And while lore
> > > has improved, the thing is still a horrible horrible ugly site (an
> > > actual fixed frame for the thread overview, and hiding that 'Reply
> > > instructions' and 'LKML Archive on lore.kernel.org' somewhow would
> > > already be a big improvement).
> > 
> > But lore allows to reference all mailinglists which are archived
> > there, while lkml.k.org is hardcoded to lkml.
> > 
> > > Also, strlen("lkml.kernel.org/r/") < strlen("lore.kernel.org/lkml/").
> > 
> > Come on ....
> 
> If the size matters, how about just putting the message id?
> Something like:
>   Link: <alpine.DEB.2.21.1907010948310.1802@nanos.tec.linutronix.de>

We could add an option to `git am` to save the Message-ID automatically.

regards,
dan carpenter