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

Re: [PATCH] commit: fix pretty-printing of messages with "\nencoding "

From
Jeff King <peff@peff.net>
Date
Mar 28, 2007, 22:15 UTC
Message-ID
<20070328221517.GA25430@coredump.intra.peff.net>
In-Reply-To
<7v7it1f29s.fsf@assigned-by-dhcp.cox.net>
On Wed, Mar 28, 2007 at 03:10:07PM -0700, Junio C Hamano wrote:
Show 6 quoted lines
> The function is correct; the only reason it may recode to
> non-utf8 is the user (or Porcelain such as qgit or gitk)
> explicitly asked to do so -- from the final output they will get
> the message in user-native encoding and without the extra
> encoding header, thus we retain the backward compatible
> behaviour before the re-encoding feature was introduced.

I see. But then why do we not simply strip the encoding header entirely, and return in native format? Why do we insert a new encoding header _only_ when there was one previously?

-Peff
Previous: Junio C Hamano
Message 3 of 3 in “commit: fix pretty-printing of messages with "\nencoding "”
  1. commit: fix pretty-printing of messages with "\nencoding "Jeff King, Mar 28, 2007
  2. Junio C HamanoMar 28, 2007
  3. Jeff KingMar 28, 2007

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.