git: d3ba089a5212 - main - Update to version 2.2.13.

[Dmitry Sivachenko]

> On 20 Apr 2021, at 02:07, Michael Gmelin <grembo at FreeBSD.org> wrote:
> 
> 
> 
>> On 20. Apr 2021, at 00:24, Dmitry Sivachenko <demon at freebsd.org> wrote:
>> 
>> 
>> 
>>> On 20 Apr 2021, at 01:17, Yuri <yuri at FreeBSD.org> wrote:
>>> 
>>> On 4/19/21 3:13 PM, Dmitry Sivachenko wrote:
>>>>    Update to version 2.2.13.
>>> 
>>> 
>>> Why didn't you mention in the commit message what port was updated?
>>> net/haproxy is one of thousands of ports and having a message like this doesn't help to understand what the change is.
>>> 
>> 
>> Hello,
>> 
>> what do you mean 'what port was updated'?  It is clean from the commit log that it is net/haproxy that was updated, only two files changed:
>>   Update to version 2.2.13.
>> ---
>> net/haproxy/Makefile | 2 +-
>> net/haproxy/distinfo | 6 +++---
>> 2 files changed, 4 insertions(+), 4 deletions(-)
>> 
>> 
>> Or may be I am missing something...
> 
> The idea is to prefix the first line of the commit with <category>/<name>:, so it’s easier to understand which port was changed when looking at a list of commits.
> 
> See here for an example of why this helps:
> https://cgit.freebsd.org/ports/log/
> 


Aha, I see now.  I used to think that commit log should describe what has changed, and commit logs are just tool.
But things changed and now we should think how commit log will look in mail client provided you read only subject line  :)