{"thread":{"id":"31579","subject":"Gitk commit order leads to unnecessarily long lines","startedAt":"2012-09-18T01:41:18Z","lastAt":"2012-09-18T01:41:18Z","messageCount":1,"participants":["Sebastian Dörner"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"199317","messageId":"CA+_kBjAWM1XHVsRa4WfDZXvtf8eJGweJhi3Rz7Sfhv390hA7WA@mail.gmail.com","threadId":"31579","inReplyTo":null,"subject":"Gitk commit order leads to unnecessarily long lines","fromName":"Sebastian Dörner","fromEmail":"sebastian@sebastian-doerner.de","sentAt":"2012-09-18T01:41:18Z","receivedAt":"2012-09-18T01:41:18Z","isPatch":false,"sender":{"key":"sebastian@sebastian-doerner.de","avatar":null},"body":"Hi,\nIt seems like the order gitk uses for the commits sometimes leads to\noverly long lines. My use case is this repository (note that this\nsvn-conversion is still WIP):\nhttp://www.sebastian-doerner.de/kompare.tgz\n\nLooking at this with \"gitk --all\" looks partly like this:\nhttp://i.imgur.com/oewTq.png\nAlmost all the commits are in one branch. Rendering the merges at the\ntop much earlier would avoid this line chaos. Interestingly, if you\njust render the relevant commits, it looks fine:\ngitk 768493d381aceffc90f132b6accb1536af8a3cc3..0ef520d910208c4d53bdd915964107b5a98cdc08\nThe problem for the current algorithm is probably the single non-merge\ncommit before the merges.\n\nAnother instance in the same repo (again gitk --all) is this part:\nhttp://i.imgur.com/0i2fF.png\nBoth the pink and right orange line merge from trunk into that kde4\nbranch. However, this is not obvious from the way it is drawn. I see\nthis problem is a bit \"softly expressed\", but I hope you see what I\nmean. I think making the merge edges shorter would also make the\nactual structure more obvious.\n\nI have no good idea how to easily fix these problems, but I don't know\nthat much about how it works currently. I see it might involve some\nmore \"intelligence\" of the rendering algorithm (forward-looking of\nsome sort). So never mind if you don't have a fast fix. But I still\nwanted to point out that the problem exists.\n\nThis might be related to this issue:\nhttp://thread.gmane.org/gmane.comp.version-control.git/18097/focus=18103\ngit version 1.7.12\n\nThank you!\n\nRegards\n\nSebastian\n"}]}