{"thread":{"id":"32146","subject":"Should --pretty=format:%b respect i18n.logoutputencoding just like normal \"git log\"?","startedAt":"2012-11-19T13:08:31Z","lastAt":"2012-11-19T17:42:48Z","messageCount":2,"participants":["Nguyen Thai Ngoc Duy","Pat Notz"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"203503","messageId":"CACsJy8Ag7wZCKeTM-fW7MUjWs=7xq7ciwhfx4kroJupwvs0dXg@mail.gmail.com","threadId":"32146","inReplyTo":null,"subject":"Should --pretty=format:%b respect i18n.logoutputencoding just like normal \"git log\"?","fromName":"Nguyen Thai Ngoc Duy","fromEmail":"pclouds@gmail.com","sentAt":"2012-11-19T13:08:31Z","receivedAt":"2012-11-19T13:08:31Z","isPatch":false,"sender":{"key":"pclouds@gmail.com","avatar":"https://avatars.githubusercontent.com/u/720?v=4"},"body":"Changes around this code in history is a bit unclear. User format\nlearns to get log encoding from a field in 177b29d (pretty.c: teach\nformat_commit_message() to reencode the output - 2010-11-02), but this\nfield is only set for --fixup and --squash (in a few commits later).\nThis makes \"git log --pretty=format:%b\" always ignore the output\nencoding config key. I don't think %b output should be different from\nnormal log output, which does respect output encoding. Pat, any\nreasons not to do it?\n-- \nDuy\n"},{"id":"203507","messageId":"CADvGaErNPyHEP029-M-UWtDUaH0xJstXUc+9FGuy-7YEUM0zpA@mail.gmail.com","threadId":"32146","inReplyTo":"CACsJy8Ag7wZCKeTM-fW7MUjWs=7xq7ciwhfx4kroJupwvs0dXg@mail.gmail.com","subject":"Re: Should --pretty=format:%b respect i18n.logoutputencoding just like normal \"git log\"?","fromName":"Pat Notz","fromEmail":"patnotz@gmail.com","sentAt":"2012-11-19T17:42:48Z","receivedAt":"2012-11-19T17:42:48Z","isPatch":false,"sender":{"key":"patnotz@gmail.com","avatar":"https://avatars.githubusercontent.com/u/45364?v=4"},"body":"On Mon, Nov 19, 2012 at 6:08 AM, Nguyen Thai Ngoc Duy <pclouds@gmail.com> wrote:\n> Changes around this code in history is a bit unclear. User format\n> learns to get log encoding from a field in 177b29d (pretty.c: teach\n> format_commit_message() to reencode the output - 2010-11-02), but this\n> field is only set for --fixup and --squash (in a few commits later).\n> This makes \"git log --pretty=format:%b\" always ignore the output\n> encoding config key. I don't think %b output should be different from\n> normal log output, which does respect output encoding. Pat, any\n> reasons not to do it?\n\nNope, that looks like it was an oversight on my part. Nice find.\n\n~ Pat\n\n> --\n> Duy\n"}]}