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

Re: Should --pretty=format:%b respect i18n.logoutputencoding just like normal "git log"?

From
Pat Notz <patnotz@gmail.com>
Date
Nov 19, 2012, 17:42 UTC
Message-ID
<CADvGaErNPyHEP029-M-UWtDUaH0xJstXUc+9FGuy-7YEUM0zpA@mail.gmail.com>
In-Reply-To
<CACsJy8Ag7wZCKeTM-fW7MUjWs=7xq7ciwhfx4kroJupwvs0dXg@mail.gmail.com>
On Mon, Nov 19, 2012 at 6:08 AM, Nguyen Thai Ngoc Duy <pclouds@gmail.com> wrote:
Show 8 quoted lines
> Changes around this code in history is a bit unclear. User format
> learns to get log encoding from a field in 177b29d (pretty.c: teach
> format_commit_message() to reencode the output - 2010-11-02), but this
> field is only set for --fixup and --squash (in a few commits later).
> This makes "git log --pretty=format:%b" always ignore the output
> encoding config key. I don't think %b output should be different from
> normal log output, which does respect output encoding. Pat, any
> reasons not to do it?
Nope, that looks like it was an oversight on my part. Nice find.
~ Pat
> --
> Duy
Previous: Nguyen Thai Ngoc Duy
Message 2 of 2 in “Should --pretty=format:%b respect i18n.logoutputencoding just like normal "git log"?”
  1. Nguyen Thai Ngoc DuyNov 19, 2012
  2. Pat NotzNov 19, 2012

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.