From: Paul Mackerras <paulus@samba.org>
To: Petr Baudis <pasky@ucw.cz>
Cc: git@vger.kernel.org
Subject: Re: Prototype git commit viewer
Date: Tue, 10 May 2005 08:12:13 +1000 [thread overview]
Message-ID: <17023.57405.35272.46557@cargo.ozlabs.ibm.com> (raw)
In-Reply-To: <20050509071341.GA3599@pasky.ji.cz>
Petr Baudis writes:
> What are its advantages to git-viz?
As a kernel developer, when I do a pull from Linus' tree, the question
I want to ask is "who has been making what changes?" That's why gitk
shows the headline and author of each of 30 commits in one screenful.
AFAICS from the screenshots, git-viz doesn't give me that density of
information (and neither did bk revtool, for that matter).
It seems to me that git-viz makes the graph topology the primary thing
and the details of the commits the secondary thing. I want it the
other way around.
Paul.
next prev parent reply other threads:[~2005-05-09 22:05 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-09 1:40 Prototype git commit viewer Paul Mackerras
2005-05-09 2:53 ` Junio C Hamano
2005-05-09 7:13 ` Petr Baudis
2005-05-09 9:25 ` Benjamin Herrenschmidt
2005-05-09 22:12 ` Paul Mackerras [this message]
2005-05-10 0:03 ` Petr Baudis
2005-05-09 18:50 ` Krzysztof Halasa
2005-05-10 0:33 ` Paul Mackerras
2005-05-10 4:54 ` Greg KH
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=17023.57405.35272.46557@cargo.ozlabs.ibm.com \
--to=paulus@samba.org \
--cc=git@vger.kernel.org \
--cc=pasky@ucw.cz \
/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).