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

[Shuah Khan <skhan@linuxfoundation.org>]

On 7/2/19 9:18 AM, James Bottomley wrote:
> On Tue, 2019-07-02 at 08:10 -0700, James Bottomley wrote:
>> On Tue, 2019-07-02 at 16:49 +0200, Thomas Gleixner wrote:
> [...]
>>> People who use the link tag today have their homebrewn scripts to
>>> add them automatically and it shouldn't be rocket science to add
>>> that to git, patchwork whatever.
>>
>> So if we find a way of automating this globally, I'm completely
>> happy. However, I would also note that whatever script does this
>> could likely also be run by you after the fact to generate the back
>> link, so foolproof automation also lessens the need to make this a
>> mandatory commit tag.
> 
> Just on this one, it looks like getting git to archive the msgid of the
> patch commit would assist any script that goes off and tries to find
> patch series and its precursors in the archives, so perhaps adding that
> would be the actionable change in all of this?
> 

Looks like two things are emerging from my original thread that aimed to
get clarification on including "Patch revision information" in commit
logs.

1. Judiciously including information from the "Patch revision info."
    in the commit log could be valuable. Don't just bloat the commit
    log with trivial change history. This is part of patch review
    process and will not require any scripting. Maybe an update to
    the patch submit guidelines documents.

2. Archiving msgid of the patch commit for reference. This one would
    require some scripting to make it easier for maintainers.

There two aren't mutually exclusive and are actionable. Let's distill
the thread discussion to the above two items as we discuss further.

thanks,
-- Shuah