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

Re: [RFC PATCH] commit: Warn about encodings unsupported by iconv.

From
Alex Riesen <raa.lkml@gmail.com>
Date
Oct 21, 2008, 06:17 UTC
Message-ID
<20081021061754.GA4656@blimp.localdomain>
In-Reply-To
<7vmygy233r.fsf@gitster.siamese.dyndns.org>
Junio C Hamano, Tue, Oct 21, 2008 02:39:36 +0200:
Show 7 quoted lines
> I actually have an alternative approach to suggest.
> 
> How about adding a new i18n.commit-reencode-logmessage option (boolean),
> and when it is set, we actually re-encode from i18n.commitencoding to
> "utf-8" before creating the commit object (and obviously we do not store
> "encoding" header in the resulting commit)?  When the conversion fails, we
> know it failed, so the warning you added does make sense in that context.

Maybe make the option a string, and allow to choose the target encoding (not only utf8, but anything user wishes)?

Previous: Junio C HamanoNext: Alexander Gavrilov
Message 3 of 4 in “commit: Warn about encodings unsupported by iconv.”
  1. commit: Warn about encodings unsupported by iconv.Alexander Gavrilov, Oct 20, 2008
  2. Junio C HamanoOct 21, 2008
  3. Alex RiesenOct 21, 2008
  4. Alexander GavrilovOct 21, 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.