Re: New Git hooks for checking file names in commit messages

[Eli Zaretskii]

> From: Arsen Arsenović <arsen@aarsen.me>
> Cc: acm@muc.de, jporterbugs@gmail.com, emacs-devel@gnu.org
> Date: Fri, 21 Apr 2023 19:50:09 +0200
> 
> Eli Zaretskii <eliz@gnu.org> writes:
> 
> >
> > No, "git reset" doesn't rebase.
> 
> No, but it means that everything above the reset point is malleable, in
> which case, you can use a rebase on it anyway (which can be reasoned
> with as a hard reset with repeated patch application).
> 
> I'm trying to say that it's unnecessary to reset entire histories to
> modify some words or formatting in commit messages.

No one was talking about "entire histories", we were talking about a
single commit that was just made, but not yet pushed.  "git reset" is
a way to undo the last commit, letting the user to make any changes
he/she wants before committing again.  So it is (MO) the easiest and
safest way of fixing such mistakes.  It is why we recommend users to
always do a "git show" before pushing, so that they could review what
is about to be pushed before actually doing so.