{"thread":{"id":"29202","subject":"i18n.commitencoding=gbk or --encoding=gbk not work with --pretty=format","startedAt":"2011-12-18T13:26:02Z","lastAt":"2011-12-18T13:26:02Z","messageCount":1,"participants":["Yuchen Deng"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"181436","messageId":"1324214762135-7105845.post@n2.nabble.com","threadId":"29202","inReplyTo":null,"subject":"i18n.commitencoding=gbk or --encoding=gbk not work with --pretty=format","fromName":"Yuchen Deng","fromEmail":"loaden@gmail.com","sentAt":"2011-12-18T13:26:02Z","receivedAt":"2011-12-18T13:26:02Z","isPatch":false,"sender":{"key":"loaden@gmail.com","avatar":null},"body":"Hi, all!\nWhen set the option i18n.commitencoding value to gbk. I found the 'git log'\nouput encoding always is the default : utf8\n\n    git log -n10 --pretty=format:\"%h %d %an %s %ci\" --topo-order --graph\nor\n    git log -n10 --encoding=utf8 --pretty=format:\"%h %d %an %s %ci\"\n--topo-order --graph\n\nBut:\n    git log --oneline\n\nworks well.\nI am from China, and the GFW thing, I can't visit git-scm.com.\nSo, Somebody can help me to report this bug?\nI am sure it's don't work for Windows (msys-git) or Linux (Chakra).\nThanks!\n\n--\nView this message in context: http://git.661346.n2.nabble.com/i18n-commitencoding-gbk-or-encoding-gbk-not-work-with-pretty-format-tp7105845p7105845.html\nSent from the git mailing list archive at Nabble.com.\n"}]}