From: Po Lu via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Stefan Kangas <stefankangas@gmail.com>
Cc: No Wayman <iarchivedmywholelife@gmail.com>, 68691@debbugs.gnu.org
Subject: bug#68691: 30.0.50; [WISHLIST] Make it easier to conform to desired commit message format
Date: Fri, 26 Jan 2024 09:27:29 +0800 [thread overview]
Message-ID: <87il3gopdq.fsf@yahoo.com> (raw)
In-Reply-To: <CADwFkmmu5Y-1uWQvANG8E6zqiTEgTFarGtjuhAVEjQAN9QPOXA@mail.gmail.com> (Stefan Kangas's message of "Thu, 25 Jan 2024 15:09:22 -0800")
Stefan Kangas <stefankangas@gmail.com> writes:
> FWIW, I'll not be working on such a mode myself, as I'd rather see that
> we promoted useful commit messages in the style of, say, the Linux
> kernel instead of the GNU ChangeLog format. It is simply redundant to
> enumerate changed files when using a modern distributed VCS like Git.
> But that's my personal opinion, and not currently that of the project.
I think part of our position is that it is far too easy to write
uninformative commit messages when one is not being forced to mentally
review the commit's contents. As with any other form of discipline,
maintaining ChangeLog discipline is an end in itself, not necessarily
something that might produce an immediate benefit. See FreeType's
experience:
https://lists.nongnu.org/archive/html/freetype-devel/2013-04/msg00046.html
https://lists.nongnu.org/archive/html/freetype-devel/2020-07/msg00032.html
A hook run before each commit is a good idea, and I plan to study how
they are written.
next prev parent reply other threads:[~2024-01-26 1:27 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-24 17:20 bug#68691: 30.0.50; [WISHLIST] Make it easier to conform to desired commit message format No Wayman
2024-01-25 23:09 ` Stefan Kangas
2024-01-26 1:27 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2024-01-26 18:44 ` Jim Porter
2024-01-28 0:44 ` Stefan Kangas
2024-01-28 6:18 ` Eli Zaretskii
2024-01-28 7:21 ` Stefan Kangas
2024-01-28 7:33 ` Eli Zaretskii
2024-01-28 8:43 ` Juri Linkov
2024-01-26 7:18 ` Eli Zaretskii
2024-01-28 1:07 ` Stefan Kangas
2024-01-28 6:21 ` Eli Zaretskii
2024-01-28 7:26 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-01-28 7:42 ` Eli Zaretskii
2024-01-28 9:04 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-01-28 9:57 ` Eli Zaretskii
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87il3gopdq.fsf@yahoo.com \
--to=bug-gnu-emacs@gnu.org \
--cc=68691@debbugs.gnu.org \
--cc=iarchivedmywholelife@gmail.com \
--cc=luangruo@yahoo.com \
--cc=stefankangas@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.