git: 44b57221ced8 - main - Update OpenBVE to version 1.8.0.2.

[Kubilay Kocak]

On 27/04/2021 1:31 am, Alexey Dokuchaev wrote:
> On Mon, Apr 26, 2021 at 09:28:42PM +1000, Kubilay Kocak wrote:
>> On 26/04/2021 9:07 pm, Alexey Dokuchaev wrote:
>>> ...
>>> commit 44b57221ced803c65ed137d495fb787537915ee6
>>> ...
>>>       Update OpenBVE to version 1.8.0.2.
>>
>> Any chance of getting cat/port: as prefixes to ports commit titles?
> 
> Admittedly, I find this format quite hard to read: every time I catch
> an exception, have to skip the first foo/bar part to get to what goes
> after, and only if it was not clear (or important to know) what is the
> port it was about, go back to the beginning.  Note that I did mention
> the port name in the first line, but in a way that does not disrupt
> the reading flow.
> 
> I'm also worried that this is needless duplication: this information
> can be inferred from the commit itself:
> 
> $ git show --pretty="" --name-only 44b5722 | xargs dirname | sort | uniq
> games/openbve
> games/openbve/files
> 
> People have asked for it because there is no path in the the subject
> line with the default git email template.  Wouldn't it be better to
> fix this rather than keep duplicating port directory in every commit?

There's value for people other than us developers, where being able to 
know what thing changed without needing to drill deeper or fetch diffs, 
is useful in various ways.

The 'commit message text' is all that should be needed, and including 
"component:" in its title, independent of the method by which the users 
may see it, including not by mail or `git`; twitter, discord, some web 
app, freshports, whatever else, encapsulates that.


> ./danfe
>