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 09:33:49 +0200 [thread overview]
Message-ID: <86jznt6heq.fsf@gnu.org> (raw)
In-Reply-To: <CADwFkmmkHz1DNpXq6vtAWKE8POEXs=CW8ZrYzgfxxO6EAKC8=g@mail.gmail.com> (message from Stefan Kangas on Sat, 27 Jan 2024 23:21:47 -0800)
> From: Stefan Kangas <stefankangas@gmail.com>
> Date: Sat, 27 Jan 2024 23:21:47 -0800
> Cc: luangruo@yahoo.com, iarchivedmywholelife@gmail.com, 68691@debbugs.gnu.org
>
> Eli Zaretskii <eliz@gnu.org> writes:
>
> > 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.
>
> I tend to agree, though what I had in mind was something simpler than
> that: to opportunistically catch some obvious errors.
>
> For example, we could highlight text going over 72/80 columns
This is already done in one of the commit hooks.
> or mark in red any line matching "^lisp/foo/bar.el" (which should be
> a mistake 99.9 % of the time).
If that names a nonexistent file, or a file with wrong leading
directories, one of the existing hooks already does catch such
mistakes.
next prev parent reply other threads:[~2024-01-28 7:33 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
2024-01-28 7:21 ` Stefan Kangas
2024-01-28 7:33 ` Eli Zaretskii [this message]
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=86jznt6heq.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.