From nobody Wed Sep 10 18:00:24 2025 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4cMT4c0W1Hz66fkW for ; Wed, 10 Sep 2025 18:00:32 +0000 (UTC) (envelope-from gperciva@tarsnap.com) Received: from mail.tarsnap.com (mail.tarsnap.com [54.86.246.204]) by mx1.freebsd.org (Postfix) with SMTP id 4cMT4b4nqrz3bQ4 for ; Wed, 10 Sep 2025 18:00:31 +0000 (UTC) (envelope-from gperciva@tarsnap.com) Authentication-Results: mx1.freebsd.org; none Received: (qmail 57896 invoked from network); 10 Sep 2025 18:00:30 -0000 Received: from unknown (HELO localhost) (127.0.0.1) by mail.tarsnap.com with SMTP; 10 Sep 2025 18:00:30 -0000 Date: Wed, 10 Sep 2025 11:00:24 -0700 From: Graham Percival To: Dmitry Salychev Cc: Tomek CEDRO , freebsd-current@freebsd.org Subject: Re: FreeBSD git weekly for 2025-09-01 to 2025-09-07 Message-ID: References: <86ikhq7qds.fsf@peasant.salychev.org> List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@FreeBSD.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <86ikhq7qds.fsf@peasant.salychev.org> X-Spamd-Bar: ---- X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:14618, ipnet:54.86.0.0/16, country:US] X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-Rspamd-Queue-Id: 4cMT4b4nqrz3bQ4 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