Date: Wed, 10 Sep 2025 11:00:24 -0700 From: Graham Percival <gperciva@tarsnap.com> To: Dmitry Salychev <dsl@freebsd.org> Cc: Tomek CEDRO <tomek@cedro.info>, freebsd-current@freebsd.org Subject: Re: FreeBSD git weekly for 2025-09-01 to 2025-09-07 Message-ID: <aMG8uASf6_BDi25P@beastie.local> In-Reply-To: <86ikhq7qds.fsf@peasant.salychev.org> References: <aMDiSmZUfwG-Q7np@beastie.local> <CAFYkXj=4NExBE3CNM7o8bYGdDWfORL8uhnyarBaWrAMpn5P4_g@mail.gmail.com> <aMEMlOcx3-8C-ifB@beastie.local> <86ikhq7qds.fsf@peasant.salychev.org>
index | next in thread | previous in thread | raw e-mail
On 2025-09-10, Dmitry Salychev wrote:
>
> I wonder whether specific keywords can be added to the commit
> messages to suggest a category/simplify classification.
Ah, I answered the earlier questions, but missed this one.
I don't think it's necessary to add anything to commit messages.
Most commit messages begin with a
prefix: blah blah blah
and those "prefixes" are very useful.
If I was going to make any requests about commit messages -- which I
wouldn't -- then I'd ask for more of them to have those prefixes.
For example, in the 2025-09-01 week, 7 commits (4.1%) did not have a
prefix. Of those,
- 2 had something similar to "prefix:" but the exact formatting was a
bit off; I can work around that in code. (added to my todo list)
- 4 didn't have any prefix but the list of modified files was clear
enough that they were classified based on the filenames (ignoring
the commit message entirely).
- 1 required manual attention because neither the commit message nor
list of files was clear. Thanks, cperciva! Admittedly 8b4e4c273 was
easy to classify manually, but I would have written one of:
release: Update main to 16
internal: Update main to 16
branches: Update main to 16
Cheers,
- Graham
home |
help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?aMG8uASf6_BDi25P>