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

Re: gitk graph routing problem

From
Paul Mackerras <paulus@samba.org>
Date
Dec 11, 2007, 22:26 UTC
Message-ID
<18271.3714.731136.272491@cargo.ozlabs.ibm.com>
In-Reply-To
<20071104104618.GA3078@steel.home>
Alex Riesen writes:
Show 7 quoted lines
> To reproduce, try running in git repo:
> 
>     gitk 02f630448e5d48e..06ea6ba9cf46ef5
> 
> Than go some pages (around 5) forward. You should notice system load
> going up rapidly. Now try paging back - and graph starts stretching
> to the right, to the point nothing fits on the screen anymore.

I finally got back to look at this. The problem is not so much the layout algorithm per se as the fact that I haven't worked out a good way to pack lots of downward-pointing arrows in without using up arbitrarily large amounts of horizontal space. You have managed to find an example where just about every commit is a merge needing one or more downward-pointing arrows.

Incidentally, gitk from the dev branch of my gitk.git repo does much better on this example, since it is able to hoist the open-circle (excluded) commits up to the row below their merge children, which looks much nicer.

Paul.
Previous: Alex RiesenNext: Alex Riesen
Message 7 of 8 in “gitk graph routing problem”
  1. Alex RiesenNov 4, 2007
  2. Paul MackerrasNov 4, 2007
  3. Junio C HamanoNov 4, 2007
  4. Alex RiesenNov 5, 2007
  5. Alex RiesenNov 5, 2007
  6. Alex RiesenNov 5, 2007
  7. Paul MackerrasDec 11, 2007
  8. Alex RiesenDec 14, 2007

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.