From: Petr Baudis <pasky@ucw.cz>
To: Paul Mackerras <paulus@samba.org>
Cc: git@vger.kernel.org
Subject: Re: Prototype git commit viewer
Date: Mon, 9 May 2005 09:13:41 +0200 [thread overview]
Message-ID: <20050509071341.GA3599@pasky.ji.cz> (raw)
In-Reply-To: <17022.49021.344841.79940@cargo.ozlabs.ibm.com>
Dear diary, on Mon, May 09, 2005 at 03:40:13AM CEST, I got a letter
where Paul Mackerras <paulus@samba.org> told me that...
> Over the weekend I hacked up a prototype viewer for git commits in
> Tk. It's called gitk and is at:
>
> http://ozlabs.org/~paulus/gitk
>
> (that's the actual script itself :).
>
> It displays a window with two panes; the upper one shows a summary of
> all the commits with a graph on the left showing the relationship of
> the commits (each dot represents a commit, with lines joining parents
> and children). The list is displayed with the most recent commit at
> the top, and parents below their children.
>
> If you click on a commit, the bottom pane shows more details of the
> commit including the commit comments.
>
> I plan to add a pane to show the list of files changed by the commit,
> and provide a way to pop up a dirdiff-style diff viewer window to view
> the actual diffs. I also plan to add a way to view the diffs between
> arbitrary points in the graph using girdiff. There is quite a lot of
> UI tweaking to be done too. However, it's already quite useful in its
> current state.
What are its advantages to git-viz?
--
Petr "Pasky" Baudis
Stuff: http://pasky.or.cz/
C++: an octopus made by nailing extra legs onto a dog. -- Steve Taylor
next prev parent reply other threads:[~2005-05-09 7:06 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 [this message]
2005-05-09 9:25 ` Benjamin Herrenschmidt
2005-05-09 22:12 ` Paul Mackerras
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=20050509071341.GA3599@pasky.ji.cz \
--to=pasky@ucw.cz \
--cc=git@vger.kernel.org \
--cc=paulus@samba.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).