From: Robin Rosenberg <robin.rosenberg.lists@dewire.com>
To: Raimund Bauer <ray007@gmx.net>
Cc: git <git@vger.kernel.org>
Subject: Re: [wishlist] graphical diff
Date: Sun, 18 Mar 2007 16:06:19 +0100 [thread overview]
Message-ID: <200703181606.20678.robin.rosenberg.lists@dewire.com> (raw)
In-Reply-To: <1174223784.5987.6.camel@localhost>
söndag 18 mars 2007 14:16 skrev Raimund Bauer:
> I think it would be really helpful (especially for newbies like me) to
> have an option like
>
> git diff --gui [revisions] <singe path spec>
>
> to fire up a graphical diff viewer (similar to what git-mergetool does).
>
> Another good place to start a graphical diff from is probably gitk from
> a context-menu for the changed files in the lower right pane.
>
> Thoughts?
>
Fine, except it is not likely to be my favourite gui. But you don't have to wait,
you can get a gui easily today.
Pipe the output to another tool. Kompare is such a tool which can take a patch
and compare it. It does not have to a single file. You can diff two trees and
compare. You'll need at kdesdk version 3.5.5 (or 3.5.6) or the patch in
http://bugs.kde.org/show_bug.cgi?id=131717 for kompare to display git diffs.
git diff HEAD^..HEAD | kompare -
As for other gui's I don't know which ones work easily out of the box.
Eclipse will soon have recursive diff mode for git. Seems to work here, so I'll probably submit it soon).
-- robin
next prev parent reply other threads:[~2007-03-18 15:04 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-18 13:16 [wishlist] graphical diff Raimund Bauer
2007-03-18 15:06 ` Robin Rosenberg [this message]
2007-03-18 23:09 ` Johannes Schindelin
2007-03-18 23:51 ` Robin Rosenberg
2007-03-19 0:09 ` Johannes Schindelin
2007-03-19 8:14 ` Raimund Bauer
2007-03-19 13:00 ` Johannes Schindelin
2007-03-19 16:44 ` Raimund Bauer
2007-03-19 16:49 ` Johannes Schindelin
2007-03-19 20:29 ` Raimund Bauer
2007-03-18 21:39 ` Christian MICHON
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=200703181606.20678.robin.rosenberg.lists@dewire.com \
--to=robin.rosenberg.lists@dewire.com \
--cc=git@vger.kernel.org \
--cc=ray007@gmx.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 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).