From: Alex Riesen <raa.lkml@gmail.com>
To: Paul Mackerras <paulus@samba.org>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
Git Mailing List <git@vger.kernel.org>
Subject: Re: gitk layout bug
Date: Mon, 21 Jan 2008 20:08:54 +0100 [thread overview]
Message-ID: <20080121190854.GA5263@steel.home> (raw)
In-Reply-To: <18324.27370.96611.769276@cargo.ozlabs.ibm.com>
Paul Mackerras, Mon, Jan 21, 2008 10:50:34 +0100:
> 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.
prev parent reply other threads:[~2008-01-21 19:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-20 1:44 gitk layout bug Linus Torvalds
2008-01-20 1:50 ` Johannes Schindelin
2008-01-20 20:30 ` Alex Riesen
2008-01-21 9:50 ` Paul Mackerras
2008-01-21 10:13 ` Johannes Sixt
2008-01-21 19:08 ` Alex Riesen [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=20080121190854.GA5263@steel.home \
--to=raa.lkml@gmail.com \
--cc=git@vger.kernel.org \
--cc=paulus@samba.org \
--cc=torvalds@linux-foundation.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).