From: bdowning@lavos.net (Brian Downing)
To: "Shawn O. Pearce" <spearce@spearce.org>
Cc: git@vger.kernel.org
Subject: Re: gitk screenshots of complex history
Date: Fri, 27 Jul 2007 08:52:38 -0500 [thread overview]
Message-ID: <20070727135238.GW21692@lavos.net> (raw)
In-Reply-To: <20070727041300.GD20052@spearce.org>
On Fri, Jul 27, 2007 at 12:13:01AM -0400, Shawn O. Pearce wrote:
> 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
prev parent reply other threads:[~2007-07-27 13:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-27 4:13 gitk screenshots of complex history Shawn O. Pearce
2007-07-27 5:20 ` Linus Torvalds
2007-07-27 5:29 ` Shawn O. Pearce
2007-07-27 5:49 ` David Kastrup
2007-07-27 13:52 ` Brian Downing [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20070727135238.GW21692@lavos.net \
--to=bdowning@lavos.net \
--cc=git@vger.kernel.org \
--cc=spearce@spearce.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.