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

Re: gitk screenshots of complex history

From
Brian Downing <bdowning@lavos.net>
Date
Jul 27, 2007, 13:52 UTC
Message-ID
<20070727135238.GW21692@lavos.net>
In-Reply-To
<20070727041300.GD20052@spearce.org>
On Fri, Jul 27, 2007 at 12:13:01AM -0400, Shawn O. Pearce wrote:
Show 9 quoted lines
> I've mentioned both on list and on #git that one of my production
> repositories has a few weird points in time.  Some folks have asked
> to see at least screenshots of the line part of the gitk output,
> as apparently they've never seen ugly history in Git.  Lucky them.
> 
> The images are rather large so I have posted them on my website
> with a bit longer explanation of each:
> 
>   http://www.spearce.org/2007/07/difficult-gitk-graphs.html
> OK, no more screenshots from *that* repository!  I don't ever want
> to run `gitk --all` there again.  Ever.

Were those graphs generated with --topo-order (the default) or --date-order? I've found complex history usually looks a lot more manageable with --date-order. Certainly the Git history is a LOT less wide with --all --date-order than --all.

Does this help your situation as well?
-bcd
Previous: David Kastrup
Message 5 of 5 in “gitk screenshots of complex history”
  1. Shawn O. PearceJul 27, 2007
  2. Linus TorvaldsJul 27, 2007
  3. Shawn O. PearceJul 27, 2007
  4. David KastrupJul 27, 2007
  5. Brian DowningJul 27, 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.