From: Stefan Kangas <stefankangas@gmail.com>
To: No Wayman <iarchivedmywholelife@gmail.com>, 68691@debbugs.gnu.org
Cc: Po Lu <luangruo@yahoo.com>
Subject: bug#68691: 30.0.50; [WISHLIST] Make it easier to conform to desired commit message format
Date: Thu, 25 Jan 2024 15:09:22 -0800 [thread overview]
Message-ID: <CADwFkmmu5Y-1uWQvANG8E6zqiTEgTFarGtjuhAVEjQAN9QPOXA@mail.gmail.com> (raw)
In-Reply-To: <87r0i6sl68.fsf@gmail.com>
No Wayman <iarchivedmywholelife@gmail.com> writes:
> Idea: Extend checkdoc or write a new minor mode that runs
> stylistic checks on commit messages.
Since we try to adhere to the GNU ChangeLog format, I think such a
linting mode would help contributors.
Copying in Po Lu, who might be interested in working on it.
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.
next prev parent reply other threads:[~2024-01-25 23:09 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 [this message]
2024-01-26 1:27 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CADwFkmmu5Y-1uWQvANG8E6zqiTEgTFarGtjuhAVEjQAN9QPOXA@mail.gmail.com \
--to=stefankangas@gmail.com \
--cc=68691@debbugs.gnu.org \
--cc=iarchivedmywholelife@gmail.com \
--cc=luangruo@yahoo.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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).