From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.bugs Subject: bug#68691: 30.0.50; [WISHLIST] Make it easier to conform to desired commit message format Date: Sun, 28 Jan 2024 11:57:24 +0200 Message-ID: <86cytl6arf.fsf@gnu.org> References: <87r0i6sl68.fsf@gmail.com> <86r0i4bm0t.fsf@gnu.org> <8634ui6kqq.fsf@gnu.org> <877cjtj4v9.fsf@yahoo.com> <86il3d6gzo.fsf@gnu.org> <8734uhj0bl.fsf@yahoo.com> Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="6032"; mail-complaints-to="usenet@ciao.gmane.io" Cc: 68691@debbugs.gnu.org, stefankangas@gmail.com, iarchivedmywholelife@gmail.com To: Po Lu Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Sun Jan 28 10:58:11 2024 Return-path: Envelope-to: geb-bug-gnu-emacs@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1rU1vX-0001NQ-68 for geb-bug-gnu-emacs@m.gmane-mx.org; Sun, 28 Jan 2024 10:58:11 +0100 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1rU1vI-0006bv-JH; Sun, 28 Jan 2024 04:57:56 -0500 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1rU1vH-0006bO-EG for bug-gnu-emacs@gnu.org; Sun, 28 Jan 2024 04:57:55 -0500 Original-Received: from debbugs.gnu.org ([2001:470:142:5::43]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1rU1vG-0005RG-Tp for bug-gnu-emacs@gnu.org; Sun, 28 Jan 2024 04:57:54 -0500 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1rU1vO-0003mw-Fk for bug-gnu-emacs@gnu.org; Sun, 28 Jan 2024 04:58:02 -0500 X-Loop: help-debbugs@gnu.org Resent-From: Eli Zaretskii Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Sun, 28 Jan 2024 09:58:02 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 68691 X-GNU-PR-Package: emacs Original-Received: via spool by 68691-submit@debbugs.gnu.org id=B68691.170643586614531 (code B ref 68691); Sun, 28 Jan 2024 09:58:02 +0000 Original-Received: (at 68691) by debbugs.gnu.org; 28 Jan 2024 09:57:46 +0000 Original-Received: from localhost ([127.0.0.1]:56612 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1rU1v8-0003mJ-78 for submit@debbugs.gnu.org; Sun, 28 Jan 2024 04:57:46 -0500 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:45522) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1rU1v3-0003lp-Eh for 68691@debbugs.gnu.org; Sun, 28 Jan 2024 04:57:45 -0500 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1rU1up-0005Nn-To; Sun, 28 Jan 2024 04:57:27 -0500 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=gnu.org; s=fencepost-gnu-org; h=References:Subject:In-Reply-To:To:From:Date: mime-version; bh=4v1T9PkE039ufIh2lHyaPWAB3iJfc+jUoHSwCDl7ebc=; b=n8MdfxViOaDJ YzRET72vXb/mBShnhwwCgP8KvqTv3sdzrqYsjy60pF8HCGzlq1hmOz94cO2xpGWRA6tuMmOLnozcT +Qfi/zUrCcsu02WP3T3vKZuJfzS3UZNVcrLEkDLl8gFGCUkZ4dbwtmJR1JsasJyYoVggJUkyUL9c/ f9oxfgHWQL6CmnJn8m6HkEF3NltB95ddW1Y0JP/ZdQMXNzz9R9QqgFDfNYnmP9hypCj1bT4ChBA8n HUkD5eVQ5PrHr508r83XL5bdhdaKmBVv4dkdUWnXxGpmYiNhiTkdwgBbiwdLPbY8zfJIaP3Fe8wqC wvx8s6TMNGAagihK2ApQ4A==; In-Reply-To: <8734uhj0bl.fsf@yahoo.com> (message from Po Lu on Sun, 28 Jan 2024 17:04:30 +0800) X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list X-BeenThere: bug-gnu-emacs@gnu.org List-Id: "Bug reports for GNU Emacs, the Swiss army knife of text editors" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Original-Sender: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Xref: news.gmane.io gmane.emacs.bugs:279078 Archived-At: > From: Po Lu > Cc: stefankangas@gmail.com, iarchivedmywholelife@gmail.com, > 68691@debbugs.gnu.org > Date: Sun, 28 Jan 2024 17:04:30 +0800 > > Eli Zaretskii writes: > > > It cannot. Format could be okay, but will not describe all of the > > changes, or describe them in a nonsensical way. > > > > OTOH, is the format below OK or not? > > > > Merge from origin/emacs-29 > > > > 53481cc9546 Fix description of when "\xNNN" is considered a unibyte character > > 1ef8b90ae06 Simplify imenu setup for {cmake,dockerfile}-ts-modes > > 7338af9c986 ; * etc/PROBLEMS: Document that GnuPG 2.4.4 solves the EasyPG > > 5483a1df99c Improve documentation of profiler commands > > fb4cf0ab46d ; Fix xref under Output Overrides in Elisp manual. > > aa6c24da61f Fix broken links to Freedesktop notifications spec > > 14d68221d26 Fix nasty cut'n'waste error in Tramp > > 51ca049608c Fix image-dired-tags-db-file void variable error > > c450eec07ff typescript-ts-mode: Skip test if tsx grammar missing > > 9841ced147f ; Fix typos > > 557ed9c0463 * admin/README: Document the run-codespell script. > > 5701f96335c * admin/README: Fix entry on coccinelle subdirectory. > > 1805f4bfd62 Add script admin/run-codespell and supporting files > > This starts with "Merge from..." So any message that begins with "Merge from" will be okay, no matter what follows it? > > Or this one: > > > > Revert "Fix typo in lispref 'Creating Strings' section" > > > > This reverts commit b825962ea840348bbde0c834ca398458a06fbb8b > > which was mistakenly installed in master instead of emacs-29. > > This starts with the word "Revert" So any message that begins with "Revert" will be okay, no matter what follows it? > > Or this one: > > > > ; Update copyright years in more files > > And this starts with a semicolon. So any message with a semicolon is okay? And if I use the same log, but without a semicolon (for whatever reasons), then the hook will abort the commit? > > How do you distinguish between the above perfectly valid examples, and > > some arbitrary text in a log message (which should be flagged as > > nonconforming)? > > The types of commit messages that don't require log messages is finite, No, it's infinite, actually. The 3 examples I've shown are just those I found in a few seconds I had.