From: Eli Zaretskii <eliz@gnu.org>
To: Stefan Kangas <stefankangas@gmail.com>
Cc: luangruo@yahoo.com, 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: Sun, 28 Jan 2024 08:18:40 +0200 [thread overview]
Message-ID: <864jey6kvz.fsf@gnu.org> (raw)
In-Reply-To: <CADwFkm=P0AAObp+f68TPTXG2fan0gU5TWyVVhH0zBraAhq7-ug@mail.gmail.com> (message from Stefan Kangas on Sat, 27 Jan 2024 16:44:24 -0800)
> Cc: No Wayman <iarchivedmywholelife@gmail.com>, 68691@debbugs.gnu.org
> From: Stefan Kangas <stefankangas@gmail.com>
> Date: Sat, 27 Jan 2024 16:44:24 -0800
>
> > A hook run before each commit is a good idea, and I plan to study how
> > they are written.
>
> We do not want a git hook for this, since we don't ask that all commits
> follow this format. It would be too heavy-handed, not to mention
> annoying when doing development locally.
I actually don't believe this can be done well enough to be useful,
i.e. with high-enough true positive rate and low enough false positive
rate. Whether a commit log message is good or bad is basically a
human judgment call; software-based solutions for that, if at all
possible, can only be based on machine-learning techniques, which
INSHO would be a ridiculously expensive solution for such a simple
problem.
next prev parent reply other threads:[~2024-01-28 6:18 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
2024-01-26 18:44 ` Jim Porter
2024-01-28 0:44 ` Stefan Kangas
2024-01-28 6:18 ` Eli Zaretskii [this message]
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=864jey6kvz.fsf@gnu.org \
--to=eliz@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.