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

[Andrea Parri <andrea.parri@amarulasolutions.com>]

> What's really useful is when the commit has a Link tag:
> 
>        https://lore.kernel.org/lkml/$MESSAGE-ID
> 
> and if the submitters provide the same kind of link in their V(N)
> submission pointing to the V(N-1) in the cover letter:
> 
>        https://lore.kernel.org/lkml/$MESSAGE-ID-V(N-1)
> 
> If it's a single patch the link can be in the patch itself after the ---
> separator. That allows a quick lookup of the history.
> 
> I also really want the change history to be at that place. i.e.
> 
>  Subject ....
> 
>  changelog text
> 
>  Tags...
>  Signed-off-by: Joe Hacker
> 
>  ---
> 
>  V3: Fixed typo
> 
>  V2: Made it work
>      https://lore.kernel.org/.... (if single patch)
> 
>  ---
> 
>  diffstat
> 
>  ---
> 
>  patch
> 
> That way tools just strip the changes section away and the maintainer does
> not have to handle it manually.
> 
> Can we pretty please agree on that format and make it mandatory?

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?

FWIW, I've been trying to conform to "lkml.kernel.org"  (which currently
seems just a redirection to "lore.kernel.org")  since [1], and I do know
of at least a few subsystems out there recommending such URLs.

Thanks,
  Andrea

[1] https://lkml.kernel.org/r/20180412115022.GL4043@hirez.programming.kicks-ass.net