From: Constantine Plotnikov <constantine.plotnikov@gmail.com>
Date: Wed, 12 Nov 2008 13:32:23 GMT
Subject: Bug: UTF-16, UCS-4 and non-existing encodings for git log result in incorrect behavior
Message-ID: <85647ef50811120532h778769ddx69f0b111dbad359a@mail.gmail.com>

If UTF-16[BE|LE] or UCS-4[BE|LE] encodings are used with git log, the
git completes successfully but commit messages and author information
are not shown. I suggest that git should fail with fatal error if such
zero producing encoding is used.

If the incorrect encoding name is used, the git log does not perform
any re-encoding, but just display commits in their native encoding. I
suggest that git should fail with fatal error in this case as well.

Regards,
Constantine