{"thread":{"id":"11680","subject":"gitk layout bug","startedAt":"2008-01-20T01:44:58Z","lastAt":"2008-01-21T19:08:54Z","messageCount":6,"participants":["Linus Torvalds","Johannes Schindelin","Alex Riesen","Paul Mackerras","Johannes Sixt"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"66007","messageId":"alpine.LFD.1.00.0801191740020.2957@woody.linux-foundation.org","threadId":"11680","inReplyTo":null,"subject":"gitk layout bug","fromName":"Linus Torvalds","fromEmail":"torvalds@linux-foundation.org","sentAt":"2008-01-20T01:44:58Z","receivedAt":"2008-01-20T01:44:58Z","isPatch":false,"sender":{"key":"torvalds@linux-foundation.org","avatar":"https://avatars.githubusercontent.com/u/1024025?v=4"},"body":"\nIn the current git repository, try this:\n\n\tgitk origin/master..origin/pu\n\nand it starts out looking ok.\n\nBut then scroll down a bit (say, press \"PageDown\" ten to twenty times), \nand scroll up again, and now that thing is totally unusable.\n\nIs it just me?\n\n\t\tLinus\n"},{"id":"66009","messageId":"alpine.LSU.1.00.0801200149450.5731@racer.site","threadId":"11680","inReplyTo":"alpine.LFD.1.00.0801191740020.2957@woody.linux-foundation.org","subject":"Re: gitk layout bug","fromName":"Johannes Schindelin","fromEmail":"johannes.schindelin@gmx.de","sentAt":"2008-01-20T01:50:47Z","receivedAt":"2008-01-20T01:50:47Z","isPatch":false,"sender":{"key":"johannes.schindelin@gmx.de","avatar":"https://avatars.githubusercontent.com/u/127790?v=4"},"body":"Hi,\n\nOn Sat, 19 Jan 2008, Linus Torvalds wrote:\n\n> In the current git repository, try this:\n> \n> \tgitk origin/master..origin/pu\n> \n> and it starts out looking ok.\n> \n> But then scroll down a bit (say, press \"PageDown\" ten to twenty times), \n> and scroll up again, and now that thing is totally unusable.\n> \n> Is it just me?\n\nJust tried; I'm getting a lot of horizontal pink lines which seem to \nextend infinitely to the right, where at first they were vertical lines...\n\nSo it is not just you, I guess.\n\nCiao,\nDscho\n"},{"id":"66047","messageId":"20080120203032.GA2891@steel.home","threadId":"11680","inReplyTo":"alpine.LFD.1.00.0801191740020.2957@woody.linux-foundation.org","subject":"Re: gitk layout bug","fromName":"Alex Riesen","fromEmail":"raa.lkml@gmail.com","sentAt":"2008-01-20T20:30:32Z","receivedAt":"2008-01-20T20:30:32Z","isPatch":false,"sender":{"key":"raa.lkml@gmail.com","avatar":"https://avatars.githubusercontent.com/u/324101?v=4"},"body":"Linus Torvalds, Sun, Jan 20, 2008 02:44:58 +0100:\n> \n> In the current git repository, try this:\n> \n> \tgitk origin/master..origin/pu\n> \n> and it starts out looking ok.\n> \n> But then scroll down a bit (say, press \"PageDown\" ten to twenty times), \n> and scroll up again, and now that thing is totally unusable.\n> \n> Is it just me?\n\nNo, it was already reported:\n\n    Message-ID: <20071104104618.GA3078@steel.home>\n"},{"id":"66104","messageId":"18324.27370.96611.769276@cargo.ozlabs.ibm.com","threadId":"11680","inReplyTo":"alpine.LFD.1.00.0801191740020.2957@woody.linux-foundation.org","subject":"Re: gitk layout bug","fromName":"Paul Mackerras","fromEmail":"paulus@samba.org","sentAt":"2008-01-21T09:50:34Z","receivedAt":"2008-01-21T09:50:34Z","isPatch":false,"sender":{"key":"paulus@samba.org","avatar":"https://avatars.githubusercontent.com/u/1606439?v=4"},"body":"Linus Torvalds writes:\n\n> In the current git repository, try this:\n> \n> \tgitk origin/master..origin/pu\n> \n> and it starts out looking ok.\n> \n> But then scroll down a bit (say, press \"PageDown\" ten to twenty times), \n> and scroll up again, and now that thing is totally unusable.\n> \n> Is it just me?\n\nNo, I have seen it occasionally (though not recently), but I've never\nbeen able to trigger it when I had some time to debug it. :/\n\nI'd be interested to know if you can trigger it with the \"dev\" branch\nof gitk, too.  The dev branch doesn't use --topo-order or\n--date-order, but instead does the topological sort itself, so the\ncold-cache case is a lot faster (and the hot-cache case goes just as\nfast as before).  And because I can now reorder the commits, I can put\neach open-circle commit just after the last merge that has it as a\nparent, which ends up looking much nicer too.\n\nPaul.\n"},{"id":"66109","messageId":"4794704D.2060607@viscovery.net","threadId":"11680","inReplyTo":"18324.27370.96611.769276@cargo.ozlabs.ibm.com","subject":"Re: gitk layout bug","fromName":"Johannes Sixt","fromEmail":"j.sixt@viscovery.net","sentAt":"2008-01-21T10:13:33Z","receivedAt":"2008-01-21T10:13:33Z","isPatch":false,"sender":{"key":"j6t@kdbg.org","avatar":"https://avatars.githubusercontent.com/u/14810926?v=4"},"body":"Paul Mackerras schrieb:\n> Linus Torvalds writes:\n> \n>> In the current git repository, try this:\n>>\n>> \tgitk origin/master..origin/pu\n>>\n>> and it starts out looking ok.\n>>\n>> But then scroll down a bit (say, press \"PageDown\" ten to twenty times), \n>> and scroll up again, and now that thing is totally unusable.\n>>\n>> Is it just me?\n> \n> No, I have seen it occasionally (though not recently), but I've never\n> been able to trigger it when I had some time to debug it. :/\n> \n> I'd be interested to know if you can trigger it with the \"dev\" branch\n> of gitk, too.  The dev branch doesn't use --topo-order or\n> --date-order, but instead does the topological sort itself, so the\n> cold-cache case is a lot faster (and the hot-cache case goes just as\n> fast as before).  And because I can now reorder the commits, I can put\n> each open-circle commit just after the last merge that has it as a\n> parent, which ends up looking much nicer too.\n\nThe dev branch is fine in this regard. In fact, this is the primary reason\nwhy I'm using it.\n\nBTW, there are still a few layout glitches, in particular, when F5\n(Update) is used after frequent rebase/cherry-pick/commit/--amend. I'll\nbug you once I know how to reproduce them.\n\n-- Hannes\n"},{"id":"66168","messageId":"20080121190854.GA5263@steel.home","threadId":"11680","inReplyTo":"18324.27370.96611.769276@cargo.ozlabs.ibm.com","subject":"Re: gitk layout bug","fromName":"Alex Riesen","fromEmail":"raa.lkml@gmail.com","sentAt":"2008-01-21T19:08:54Z","receivedAt":"2008-01-21T19:08:54Z","isPatch":false,"sender":{"key":"raa.lkml@gmail.com","avatar":"https://avatars.githubusercontent.com/u/324101?v=4"},"body":"Paul Mackerras, Mon, Jan 21, 2008 10:50:34 +0100:\n> I'd be interested to know if you can trigger it with the \"dev\" branch\n> of gitk, too.  The dev branch doesn't use --topo-order or\n> --date-order, but instead does the topological sort itself, so the\n> cold-cache case is a lot faster (and the hot-cache case goes just as\n> fast as before).  And because I can now reorder the commits, I can put\n> each open-circle commit just after the last merge that has it as a\n> parent, which ends up looking much nicer too.\n\nIt is better, but sometimes the layout seem to be a bit too\n\"aggressively cleaned up\": there are just merges and arrows pointing\nin all directions but very few of real information.\n"}]}