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

Re: [RFC/PATCH] git-shortlog: respect i18n.logOutputEncoding config setting

From
Junio C Hamano <gitster@pobox.com>
Date
Mar 22, 2009, 19:26 UTC
Message-ID
<7v7i2h5pfh.fsf@gitster.siamese.dyndns.org>
In-Reply-To
<20090322113438.GK27459@genesis.frugalware.org>
Miklos Vajna <vmiklos@frugalware.org> writes:
Show 5 quoted lines
> On Fri, Feb 20, 2009 at 02:12:38AM +0100, Miklos Vajna <vmiklos@frugalware.org> wrote:
>> As git-shortlog can be used as a filter as well, we do not really have
>> the encoding info to do a reencode_string(), but in case
>> i18n.logOutputEncoding is set, we can try to convert to the given value
>> from utf-8.

It is unclear what you want to say in these for lines. Do you mean "when used to generate logs by itself this patch improves the behaviour by making the output consistent with what "git log" does, but it does the same mangling when used as a filter without knowing the log encoding and potentially screw people over who have been depending on it not to convert the encoding"? Or something else?

Previous: Miklos VajnaNext: Miklos Vajna
Message 3 of 4 in “git-shortlog: respect i18n.logOutputEncoding config setting”
  1. git-shortlog: respect i18n.logOutputEncoding config settingMiklos Vajna, Feb 20, 2009
  2. Miklos VajnaMar 22, 2009
  3. Junio C HamanoMar 22, 2009
  4. Miklos VajnaMar 22, 2009

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.