bug#68691: 30.0.50; [WISHLIST] Make it easier to conform to desired commit message format

[Stefan Kangas]

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, or mark
in red any line matching "^lisp/foo/bar.el" (which should be a mistake
99.9 % of the time).  Stuff like that.

I'm not sure that it will be hugely useful in the end, but it might be
worth a try to hack something up.