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

Re: i18n.logToUTF8: convert commit log message to UTF-8

From
Johannes Schindelin <johannes.schindelin@gmx.de>
Date
Dec 24, 2006, 14:18 UTC
Message-ID
<Pine.LNX.4.63.0612241505290.19693@wbgn013.biozentrum.uni-wuerzburg.de>
Hi,

I don't like the convention to add the encoding after a trailing NUL. I'd rather have it as an "encoding blabl" header like the author and committer headers. I.e.

-- snip -- tree 519fba5ec35f25cbac7f46574f214fb5eb95d2c8 parent 41c7c86ccbcb846cacf48c5e283983fa797cf37b author Johannes Schindelin <Johannes.Schindelin@gmx.de> 1166969650 +0100 committer Johannes Schindelin <Johannes.Schindelin@gmx.de> 1166969650 +0100 encoding latin1

    git-commit-tree: add encoding header if commitEncoding != utf-8
-- snap --
Our log routines all grok these commit objects.

And I would prefer commit-tree to fail if we explicitely ask for conversion to UTF-8, but NO_ICONV is set, or reencoding fails for other reasons.

Ciao, Dscho

Next: Johannes Schindelin
Message 1 of 6 in “Re: i18n.logToUTF8: convert commit log message to UTF-8”
  1. Johannes SchindelinDec 24, 2006
  2. commit encoding: store it in commit header rather than mucking with NULJohannes Schindelin, Dec 24, 2006
  3. Junio C HamanoDec 25, 2006
  4. Johannes SchindelinDec 25, 2006
  5. Junio C HamanoDec 25, 2006
  6. Jakub NarebskiDec 25, 2006

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.