Re: Use of "Action stamps" in commit messages

[Andy Moreton <andrewjmoreton@gmail.com>]

On Fri 13 Jul 2018, Eli Zaretskii wrote:

>> From: Andy Moreton <andrewjmoreton@gmail.com>
>> Date: Fri, 13 Jul 2018 13:59:32 +0100
>> 
>> The Linux kernel convention is nicer: the (shortened) commit id,
>> followed by a space and the commit summary line, e.g.
>> 
>> Fixes: 1222ff5275 ("Don't skip epg-tests even with gpg 2.0 (Bug#23561)")
>
> We wanted an ID that is not specific to Git, having learned that a
> hard way from the period we used bzr revision numbers.

Using the summary line of the commit message is still useful to help
identify the right changeset (as long as you train popel to stop writing
bad commit messages like "fix last commit").

>> This ensures that the format is human readable, is easy to parse for
>> scripting, and identifies the right commit even if the shortened commit
>> id is not unique.
>
> They will stop being useful if we ever change our VCS.

That is unlikely for the forseeable future.

    AndyM