From: Ingo Molnar <mingo@elte.hu>
To: Olivier Andrieu <oandrieu@nerim.net>
Cc: git@vger.kernel.org
Subject: Re: git-viz tool for visualising commit trees
Date: Thu, 21 Apr 2005 16:38:40 +0200 [thread overview]
Message-ID: <20050421143840.GA14059@elte.hu> (raw)
In-Reply-To: <20050421.155519.112619323.oandrieu@nerim.net>
* Olivier Andrieu <oandrieu@nerim.net> wrote:
> Yes, git-viz uses the `dot' program from the graphviz package (it's in
> Fedora Extra too I believe).
ah - that resolved all issues and i'm now running git-viz without any
problems.
I just checked how the kernel repository looks like with it, and i'm
impressed! The GUI is top-notch, and the whole graph output and
navigation is very mature visually. Kudos!
a couple of suggestions that are in the 'taste' category:
- isnt left-to-right layout the more natural thing instead of top-down
(as it aligns with the reading direction)? It's selectable in the
preferences, but you might want to make it default. OTOH, top-down
creates a more compressed view of the graph.
- there doesnt seem to be any performance difference between non-colored
and colored rendering - so you might as well want to make 'color by
author' (or color by branch) the default coloring, instead of
uncolored?
- naming the boxes by key is quite meaningless. It would be more
informative to see the author's email shortcuts in the boxes. Also, it
would be nice to see some simple graphical feedback about the size and
scope of a changeset, without having to zoom on it.
i guess you know it, and i'm definitely not complaining about prototype
code, but rendering is quite slow: drawing the 340 changesets in the
current kernel repository takes 15 seconds on a 2 GHz P4. Drawing the
full kernel history (63,000 changesets) would take more than 45 minutes
on this box.
the current rate of kernel development is ~2000 changesets per month, so
drawing the kernel history will get 3 seconds slower every day - it will
exceed 1 minute in 20 days, so this will become a pressing issue quite
soon i suspect.
Ingo
next prev parent reply other threads:[~2005-04-21 14:34 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-17 19:48 git-viz tool for visualising commit trees Petr Baudis
2005-04-20 10:08 ` Ingo Molnar
2005-04-20 19:45 ` Petr Baudis
2005-04-20 20:00 ` Olivier Andrieu
2005-04-21 1:42 ` Olivier Andrieu
2005-04-21 9:21 ` Ingo Molnar
2005-04-21 10:47 ` Remi Vanicat
2005-04-21 11:31 ` Olivier Andrieu
2005-04-21 13:02 ` Ingo Molnar
2005-04-21 13:15 ` Vincent Hanquez
2005-04-21 13:55 ` Olivier Andrieu
2005-04-21 14:38 ` Ingo Molnar [this message]
2005-04-21 14:45 ` Ingo Molnar
2005-04-21 14:47 ` Ingo Molnar
2005-04-21 16:45 ` Petr Baudis
2005-04-21 20:14 ` Olivier Andrieu
2005-04-21 22:06 ` Ingo Molnar
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=20050421143840.GA14059@elte.hu \
--to=mingo@elte.hu \
--cc=git@vger.kernel.org \
--cc=oandrieu@nerim.net \
/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.