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

Re: gitk layout bug

From
Alex Riesen <raa.lkml@gmail.com>
Date
Jan 21, 2008, 19:08 UTC
Message-ID
<20080121190854.GA5263@steel.home>
In-Reply-To
<18324.27370.96611.769276@cargo.ozlabs.ibm.com>
Paul Mackerras, Mon, Jan 21, 2008 10:50:34 +0100:
Show 7 quoted lines
> I'd be interested to know if you can trigger it with the "dev" branch
> of gitk, too.  The dev branch doesn't use --topo-order or
> --date-order, but instead does the topological sort itself, so the
> cold-cache case is a lot faster (and the hot-cache case goes just as
> fast as before).  And because I can now reorder the commits, I can put
> each open-circle commit just after the last merge that has it as a
> parent, which ends up looking much nicer too.

It is better, but sometimes the layout seem to be a bit too "aggressively cleaned up": there are just merges and arrows pointing in all directions but very few of real information.

Previous: Johannes Sixt
Message 6 of 6 in “gitk layout bug”
  1. Linus TorvaldsJan 20, 2008
  2. Johannes SchindelinJan 20, 2008
  3. Alex RiesenJan 20, 2008
  4. Paul MackerrasJan 21, 2008
  5. Johannes SixtJan 21, 2008
  6. Alex RiesenJan 21, 2008

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.