Re: Bug: UTF-16, UCS-4 and non-existing encodings for git log result in incorrect behavior

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi,

On Wed, 12 Nov 2008, Constantine Plotnikov wrote:

> 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.

Have you set the correct encoding with i18n.commitEncoding?  If not, you 
should not be surprised: Git's default encoding is UTF-8, and that fact is 
well documented, AFAICT.

Ciao,
Dscho

--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Linux Kernel Development]     [Gcc Help]     [IETF Annouce]     [DCCP]     [Netdev]     [Networking]     [Security]     [V4L]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux SCSI]     [Fedora Users]

  Powered by Linux