git/list[1] front-page[2] threads[3] people[4] search[5] about
 

i18n.commitencoding=gbk or --encoding=gbk not work with --pretty=format

From
YDYuchen Deng <loaden@gmail.com>
Date
Dec 18, 2011, 13:26 UTC
Message-ID
<1324214762135-7105845.post@n2.nabble.com>

Hi, all! When set the option i18n.commitencoding value to gbk. I found the 'git log' ouput encoding always is the default : utf8

    git log -n10 --pretty=format:"%h %d %an %s %ci" --topo-order --graph
or
    git log -n10 --encoding=utf8 --pretty=format:"%h %d %an %s %ci"
--topo-order --graph
But:
    git log --oneline

works well. I am from China, and the GFW thing, I can't visit git-scm.com. So, Somebody can help me to report this bug? I am sure it's don't work for Windows (msys-git) or Linux (Chakra). Thanks!

-- View this message in context: http://git.661346.n2.nabble.com/i18n-commitencoding-gbk-or-encoding-gbk-not-work-with-pretty-format-tp7105845p7105845.html Sent from the git mailing list archive at Nabble.com.

Message 1 of 1 in “i18n.commitencoding=gbk or --encoding=gbk not work with --pretty=format”
  1. Yuchen DengDec 18, 2011

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.