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

Forcing encoding for "git commit"

From
CPConstantine Plotnikov <constantine.plotnikov@gmail.com>
Date
Nov 11, 2008, 17:10 UTC
Message-ID
<85647ef50811110910p7b40fd5dhcd79f8ae38709b95@mail.gmail.com>

I would like to see a possibility to force encoding for the "git commit" command. Currently only way to change encoding used by "git commit" is to set "i18n.commitencoding" configuration variable. But there is no way to override this variable for the specific commit like it is possible for "show" and "log" commands.

This would be useful when git is invoked from the tools. Currently tools have to query configuration variable and to encode message according to the value of the variable. And it might happen that not all characters produced by tool are supported by target encoding. Forcing the encoding, would have allowed the tool use the suitable encoding without changing user preferences.

Regards, Constantine

Message 1 of 1 in “Forcing encoding for "git commit"”
  1. Constantine PlotnikovNov 11, 2008

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.