bug#9531: md5sum: confusing documentation for file type output

[Jim Meyering]

Jim Meyering wrote:

> Reuben Thomas wrote:
>
>> I attach a patch which makes simpler changes than those I suggested
>> before. In particular, for the man page I just replaced "` '" with
>> "space" because I can't see a way to put a non-breaking space into
>> help text which will then also work in the man page after going
>> through help2man (perhaps a Unicode non-breaking space would work, but
>> it doesn't seem sensible to try!).
>>
>>>From bd0ed380c7050a1b55fca71da075fd9853442b1c Mon Sep 17 00:00:00 2001
>> From: Reuben Thomas <address@hidden>
>> Date: Sat, 17 Sep 2011 16:05:17 +0100
>> Subject: [PATCH] md5sum: clarify what is meant by binary/text flag.
>>
>>         src/md5sum.c: Clarify that we are talking about input mode.
>>         doc/coreutils.texi: Ditto.
>
> Thanks.
> I've applied that with the log adjusted to conform:
>
>     doc: clarify what is meant by md5sum's binary/text flag
>
>     * src/md5sum.c (usage): Clarify that we are talking about input mode.
>     * doc/coreutils.texi (md5sum invocation): Ditto.

Rats.
I made those changes in a COMMIT_EDITMSG buffer editor,
and then wrote the above reply.  Then I pushed your commit,
but without realizing I had never actually amended the commit.
My editor buffer was still there (just buried).

Looks like I need a local pre-push hook that would check
for a pending operation like that.