{"thread":{"id":"34649","subject":"gitk: \"Can't parse git log output: { }\"","startedAt":"2013-08-09T06:31:53Z","lastAt":"2013-08-11T11:20:07Z","messageCount":3,"participants":["Peter Krefting","Thomas Rast"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"224881","messageId":"alpine.DEB.2.00.1308090727340.3907@ds9.cixit.se","threadId":"34649","inReplyTo":null,"subject":"gitk: \"Can't parse git log output: { }\"","fromName":"Peter Krefting","fromEmail":"peter@softwolves.pp.se","sentAt":"2013-08-09T06:31:53Z","receivedAt":"2013-08-09T06:31:53Z","isPatch":false,"sender":{"key":"peter@softwolves.pp.se","avatar":"https://avatars.githubusercontent.com/u/990764?v=4"},"body":"Hi!\n\nIn my local clone of git.git, currently with the v1.8.4-rc2 tag \nchecked out and built (and installed on the system), starting up gitk \nyields an empty window, with a dialog in front of it:\n\n   error\n\n   Can't parse git log output: { }\n\n   [ OK ]\n\nHas anyone else seen this, and know what might have happened? I do not \nget the behaviour in other repositories (including other clones of \ngit.git), only this particular one.\n\n-- \n\\\\// Peter - http://www.softwolves.pp.se/\n"},{"id":"224886","messageId":"87a9kr1e7i.fsf@linux-k42r.v.cablecom.net","threadId":"34649","inReplyTo":"alpine.DEB.2.00.1308090727340.3907@ds9.cixit.se","subject":"Re: gitk: \"Can't parse git log output: { }\"","fromName":"Thomas Rast","fromEmail":"trast@inf.ethz.ch","sentAt":"2013-08-09T08:05:37Z","receivedAt":"2013-08-09T08:05:37Z","isPatch":false,"sender":{"key":"tr@thomasrast.ch","avatar":"https://avatars.githubusercontent.com/u/153510?v=4"},"body":"Peter Krefting <peter@softwolves.pp.se> writes:\n\n> Hi!\n>\n> In my local clone of git.git, currently with the v1.8.4-rc2 tag\n> checked out and built (and installed on the system), starting up gitk\n> yields an empty window, with a dialog in front of it:\n>\n>   error\n>\n>   Can't parse git log output: { }\n>\n>   [ OK ]\n>\n> Has anyone else seen this, and know what might have happened? I do not\n> get the behaviour in other repositories (including other clones of\n> git.git), only this particular one.\n\nHave you tried moving away .git/gitk.cache?\n\nIf that fixes it, perhaps you can share it for inspection.\n\n-- \nThomas Rast\ntrast@{inf,student}.ethz.ch\n"},{"id":"225054","messageId":"alpine.DEB.2.00.1308111219340.2954@ds9.cixit.se","threadId":"34649","inReplyTo":"87a9kr1e7i.fsf@linux-k42r.v.cablecom.net","subject":"Re: gitk: \"Can't parse git log output: { }\"","fromName":"Peter Krefting","fromEmail":"peter@softwolves.pp.se","sentAt":"2013-08-11T11:20:07Z","receivedAt":"2013-08-11T11:20:07Z","isPatch":false,"sender":{"key":"peter@softwolves.pp.se","avatar":"https://avatars.githubusercontent.com/u/990764?v=4"},"body":"Thomas Rast:\n\n> Have you tried moving away .git/gitk.cache?\n> If that fixes it, perhaps you can share it for inspection.\n\nYes, I did, just after I sent off that email. It did not fix the \nproblem, however.\n\n-- \n\\\\// Peter - http://www.softwolves.pp.se/\n"}]}