On 2025-07-09 23:34, Tomas Volf wrote:
The commit message’s purpose isn’t to enable people to avoid reading the
diff; that’s an impossible goal. It’s to contextualize the diff.
Which, btw, most of the Guix commits DO NOT do.
I believe we should spend more time in the space between the commit
headline and the part when the files are listed, which in most Guix
commits is empty.
For me, context is very important. When I git-blame something and the
only data I get back is:
gnu: Fix thing.
* file (thing): Fix it.
It's as good as an empty commit message.
I guess with the new codeberg approach, the "Closes #XXX" might help
adding some context but I'd still prefer if people spent some time
explaining the intent and the approach of their changes.
Just adding my two cents here.
I advocated against the changelog format, but I'm ok some
less-syntax-heavy version of it. Which I guess is what we are doing in
Guix somehow, but that has to be standardized because there is some
subjectivity about it. Some committers are very picky, others are not.
Cheers,
Ekaitz
