Please use portname in first line of git commit message (git: 2a0f957e6215 - main - Update to upstream release 56.1.0.)

Adriaan de Groot adridg at freebsd.org
Tue Apr 13 13:13:51 UTC 2021


On Tuesday, 13 April 2021 07:37:05 CEST Thomas Zander wrote:
> The branch main has been updated by riggs:
> 
> URL:
> https://cgit.FreeBSD.org/ports/commit/?id=2a0f957e621567aa84ff55748d3f59781
> af43d90
> 
> commit 2a0f957e621567aa84ff55748d3f59781af43d90
> Author:     Thomas Zander <riggs at FreeBSD.org>
> AuthorDate: 2021-04-11 15:55:24 +0000
> Commit:     Thomas Zander <riggs at FreeBSD.org>
> CommitDate: 2021-04-13 05:36:40 +0000
> 
>     Update to upstream release 56.1.0.


The git email doesn't know what paths have been committed, and "just" uses the 
first line of the commit message. Many people now use

	<category>/<port>: <change summary>

as the first line of the commit message, also because "git log" doesn't show 
files by default, and convenient git-history viewers like gitk and qgit show 
the first line of the commit message in overviews. Using this format for the 
first line of a commit message (followed by one blank line) helps all 
consumers of the git tree -- you can spot a couple by me that do *not* follow 
this format as well, that was before I realised that "this can be better". (It 
does take a while to develop the muscle memory to do it this way).

[ade]
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 659 bytes
Desc: This is a digitally signed message part.
URL: <http://lists.freebsd.org/pipermail/dev-commits-ports-all/attachments/20210413/2d67b843/attachment.sig>


More information about the dev-commits-ports-all mailing list