{"thread":{"id":"10638","subject":"gitk graph routing problem","startedAt":"2007-11-04T10:46:18Z","lastAt":"2007-12-14T22:29:31Z","messageCount":8,"participants":["Alex Riesen","Paul Mackerras","Junio C Hamano"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"58243","messageId":"20071104104618.GA3078@steel.home","threadId":"10638","inReplyTo":null,"subject":"gitk graph routing problem","fromName":"Alex Riesen","fromEmail":"raa.lkml@gmail.com","sentAt":"2007-11-04T10:46:18Z","receivedAt":"2007-11-04T10:46:18Z","isPatch":false,"sender":{"key":"raa.lkml@gmail.com","avatar":"https://avatars.githubusercontent.com/u/324101?v=4"},"body":"To reproduce, try running in git repo:\n\n gitk 02f630448e5d48e..06ea6ba9cf46ef5\n\nThan go some pages (around 5) forward. You should notice system load\ngoing up rapidly. Now try paging back - and graph starts stretching\nto the right, to the point nothing fits on the screen anymore.\n\nGitk as of commit 7388bcbc5431552718dde5c3259d861d2fa75a12 in git\nrepository. Git - v1.5.3.5-551-g02f6304 (terse fetch output and some\n*really* unrelated local modifications. Anyway, the gitk is the same).\nBisect points to or around 6e8c87070306a757c4d7fd2c55cca3a90fe140c7\n\"gitk: Establish and use global left-to-right ordering for commits\".\nIt loops heavily at this commit and looks broken in all subsequent\ncommits.\n\nLast know good was 3244729aac7515c. The master of gitk repo is ok too.\n"},{"id":"58312","messageId":"18222.15870.945694.238217@cargo.ozlabs.ibm.com","threadId":"10638","inReplyTo":"20071104104618.GA3078@steel.home","subject":"Re: gitk graph routing problem","fromName":"Paul Mackerras","fromEmail":"paulus@samba.org","sentAt":"2007-11-04T21:47:42Z","receivedAt":"2007-11-04T21:47:42Z","isPatch":false,"sender":{"key":"paulus@samba.org","avatar":"https://avatars.githubusercontent.com/u/1606439?v=4"},"body":"Alex Riesen writes:\n\n> To reproduce, try running in git repo:\n> \n> gitk 02f630448e5d48e..06ea6ba9cf46ef5\n\nI can't reproduce it here, as my clone of the git repo doesn't have\n02f630448e5d48e in it, even after updating...\n\nPaul.\n"},{"id":"58321","messageId":"7vzlxtr4bu.fsf@gitster.siamese.dyndns.org","threadId":"10638","inReplyTo":"18222.15870.945694.238217@cargo.ozlabs.ibm.com","subject":"Re: gitk graph routing problem","fromName":"Junio C Hamano","fromEmail":"gitster@pobox.com","sentAt":"2007-11-04T23:14:29Z","receivedAt":"2007-11-04T23:14:29Z","isPatch":false,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"Paul Mackerras writes:\n\n> Alex Riesen writes:\n>\n>> To reproduce, try running in git repo:\n>> \n>> gitk 02f630448e5d48e..06ea6ba9cf46ef5\n>\n> I can't reproduce it here, as my clone of the git repo doesn't have\n> 02f630448e5d48e in it, even after updating...\n\nHeh, me neither ;-).\n"},{"id":"58328","messageId":"20071105005349.GA5355@steel.home","threadId":"10638","inReplyTo":"7vzlxtr4bu.fsf@gitster.siamese.dyndns.org","subject":"Re: gitk graph routing problem","fromName":"Alex Riesen","fromEmail":"raa.lkml@gmail.com","sentAt":"2007-11-05T00:53:49Z","receivedAt":"2007-11-05T00:53:49Z","isPatch":false,"sender":{"key":"raa.lkml@gmail.com","avatar":"https://avatars.githubusercontent.com/u/324101?v=4"},"body":"Junio C Hamano, Mon, Nov 05, 2007 00:14:29 +0100:\n> Paul Mackerras writes:\n> \n> > Alex Riesen writes:\n> >\n> >> To reproduce, try running in git repo:\n> >> \n> >> gitk 02f630448e5d48e..06ea6ba9cf46ef5\n> >\n> > I can't reproduce it here, as my clone of the git repo doesn't have\n> > 02f630448e5d48e in it, even after updating...\n> \n> Heh, me neither ;-).\n\nStupid me. Will follow up with a link to the archived repo in private mail.\n"},{"id":"58330","messageId":"20071105011700.GB5355@steel.home","threadId":"10638","inReplyTo":"20071105005349.GA5355@steel.home","subject":"Re: gitk graph routing problem","fromName":"Alex Riesen","fromEmail":"raa.lkml@gmail.com","sentAt":"2007-11-05T01:17:00Z","receivedAt":"2007-11-05T01:17:00Z","isPatch":false,"sender":{"key":"raa.lkml@gmail.com","avatar":"https://avatars.githubusercontent.com/u/324101?v=4"},"body":"Alex Riesen, Mon, Nov 05, 2007 01:53:49 +0100:\n> Junio C Hamano, Mon, Nov 05, 2007 00:14:29 +0100:\n> > Paul Mackerras writes:\n> > \n> > > Alex Riesen writes:\n> > >\n> > >> To reproduce, try running in git repo:\n> > >> \n> > >> gitk 02f630448e5d48e..06ea6ba9cf46ef5\n> > >\n> > > I can't reproduce it here, as my clone of the git repo doesn't have\n> > > 02f630448e5d48e in it, even after updating...\n> > \n> > Heh, me neither ;-).\n> \n> Stupid me. Will follow up with a link to the archived repo in private mail.\n> \n\nhttp://ftp-tmp:ftp-tmp@h877881.stratoserver.net/~ftp-tmp/break-gitk.git.tar.bz2\n\nIts around 60mb.\n"},{"id":"58331","messageId":"20071105011907.GC5355@steel.home","threadId":"10638","inReplyTo":"20071105011700.GB5355@steel.home","subject":"Re: gitk graph routing problem","fromName":"Alex Riesen","fromEmail":"raa.lkml@gmail.com","sentAt":"2007-11-05T01:19:07Z","receivedAt":"2007-11-05T01:19:07Z","isPatch":false,"sender":{"key":"raa.lkml@gmail.com","avatar":"https://avatars.githubusercontent.com/u/324101?v=4"},"body":"Alex Riesen, Mon, Nov 05, 2007 02:17:00 +0100:\n> Alex Riesen, Mon, Nov 05, 2007 01:53:49 +0100:\n> > Junio C Hamano, Mon, Nov 05, 2007 00:14:29 +0100:\n> > > Paul Mackerras writes:\n> > > \n> > > > Alex Riesen writes:\n> > > >\n> > > >> To reproduce, try running in git repo:\n> > > >> \n> > > >> gitk 02f630448e5d48e..06ea6ba9cf46ef5\n> > > >\n> > > > I can't reproduce it here, as my clone of the git repo doesn't have\n> > > > 02f630448e5d48e in it, even after updating...\n> > > \n> > > Heh, me neither ;-).\n> > \n> > Stupid me. Will follow up with a link to the archived repo in private mail.\n> > \n\nand of course, I send it to everyone... Ach, well. Will keep it for a\nweek, or until it is reproduced somewhere else. Whichever comes first.\n"},{"id":"62827","messageId":"18271.3714.731136.272491@cargo.ozlabs.ibm.com","threadId":"10638","inReplyTo":"20071104104618.GA3078@steel.home","subject":"Re: gitk graph routing problem","fromName":"Paul Mackerras","fromEmail":"paulus@samba.org","sentAt":"2007-12-11T22:26:10Z","receivedAt":"2007-12-11T22:26:10Z","isPatch":false,"sender":{"key":"paulus@samba.org","avatar":"https://avatars.githubusercontent.com/u/1606439?v=4"},"body":"Alex Riesen writes:\n\n> To reproduce, try running in git repo:\n> \n> gitk 02f630448e5d48e..06ea6ba9cf46ef5\n> \n> Than go some pages (around 5) forward. You should notice system load\n> going up rapidly. Now try paging back - and graph starts stretching\n> to the right, to the point nothing fits on the screen anymore.\n\nI finally got back to look at this. The problem is not so much the\nlayout algorithm per se as the fact that I haven't worked out a good\nway to pack lots of downward-pointing arrows in without using up\narbitrarily large amounts of horizontal space. You have managed to\nfind an example where just about every commit is a merge needing one\nor more downward-pointing arrows.\n\nIncidentally, gitk from the dev branch of my gitk.git repo does much\nbetter on this example, since it is able to hoist the open-circle\n(excluded) commits up to the row below their merge children, which\nlooks much nicer.\n\nPaul.\n"},{"id":"63217","messageId":"20071214222931.GB4943@steel.home","threadId":"10638","inReplyTo":"18271.3714.731136.272491@cargo.ozlabs.ibm.com","subject":"Re: gitk graph routing problem","fromName":"Alex Riesen","fromEmail":"raa.lkml@gmail.com","sentAt":"2007-12-14T22:29:31Z","receivedAt":"2007-12-14T22:29:31Z","isPatch":false,"sender":{"key":"raa.lkml@gmail.com","avatar":"https://avatars.githubusercontent.com/u/324101?v=4"},"body":"Paul Mackerras, Tue, Dec 11, 2007 23:26:10 +0100:\n> Alex Riesen writes:\n> \n> > To reproduce, try running in git repo:\n> > \n> > gitk 02f630448e5d48e..06ea6ba9cf46ef5\n> > \n> > Than go some pages (around 5) forward. You should notice system load\n> > going up rapidly. Now try paging back - and graph starts stretching\n> > to the right, to the point nothing fits on the screen anymore.\n> \n> I finally got back to look at this. The problem is not so much the\n> layout algorithm per se as the fact that I haven't worked out a good\n> way to pack lots of downward-pointing arrows in without using up\n> arbitrarily large amounts of horizontal space. You have managed to\n> find an example where just about every commit is a merge needing one\n> or more downward-pointing arrows.\n> \n> Incidentally, gitk from the dev branch of my gitk.git repo does much\n> better on this example, since it is able to hoist the open-circle\n> (excluded) commits up to the row below their merge children, which\n> looks much nicer.\n\ncould you point to a specific commit where it does that?\n\nBecause the current head of dev branch at //git.kernel.org/pub/scm/gitk/gitk\n(3de07118f0993e6f7bc7ce02276751795d80b877) does not look any\ndifferent and still almost locks up drawing all the horizontal lines.\n"}]}