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

Re: [gitk PATCH] gitk: Disable log.decorate config

From
Jeff King <peff@peff.net>
Date
Mar 20, 2010, 05:34 UTC
Message-ID
<20100320053404.GA12625@coredump.intra.peff.net>
In-Reply-To
<1269038663-11025-1-git-send-email-santi@agolina.net>
On Fri, Mar 19, 2010 at 11:44:23PM +0100, Santi Béjar wrote:
> Since eb73445 (Add `log.decorate' configuration variable., 2010-02-17)
> the log output changes if log.decorate is set. Gitk is unable to
> understand the new output (it returns the error: "Can't parse git log
> output: {commit $sha1 $sha2...}), so disable it with --no-decorate.

log.decorate is still in "next". My understanding was that it was not going to graduate to "master" until this issue had been resolved, and that the current plan was to disable config decoration for --pretty=raw. That would solve the issue without any effort on the part of gitk.

-Peff
Previous: Santi Béjar
Message 4 of 4 in “gitk: Disable log.decorate config”
  1. gitk: Disable log.decorate configSanti Béjar, Mar 19, 2010
  2. Paul MackerrasMar 20, 2010
  3. Santi BéjarMar 20, 2010
  4. Jeff KingMar 20, 2010

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.