Re: [PATCH 3/3] Do not create commits whose message contains NUL
- From
Miles Bader <miles@gnu.org>
- Date
- Dec 15, 2011, 01:04 UTC
- Message-ID
- <CADCnXoaqEXJV+Mb1=nQge_bjA3H6R7=BPt213CKLX55zyTHEtg@mail.gmail.com>
- In-Reply-To
- <1323871699-8839-4-git-send-email-pclouds@gmail.com>
> + commitWideEncoding:: > + Advice shown when linkgit::git-commit[1] refuses to > + proceed because there are NULs in commit message. > + Default: true.
Although "wide encoding" is a reasonable guess at cause of embedded zero characters (and so a useful term for diagnostic messages, as it can help users identify the problem in their environment which is causing such zero bytes), it's really only a guess in most cases...
Shouldn't the variable be named based on what it actually does, which is allow zero-bytes in commit messages...?
-Miles
-- Cat is power. Cat is peace.