git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "David Aguilar" <davvid@gmail.com>
To: "Peter Karlsson" <peter@softwolves.pp.se>
Cc: "Git Mailing List" <git@vger.kernel.org>
Subject: Re: External diff viewer and stage/merge tool and git-gui?
Date: Tue, 3 Jun 2008 03:56:03 -0700	[thread overview]
Message-ID: <402731c90806030356r1ea4317vef40b6449f4fca16@mail.gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0806030819310.31572@ds9.cixit.se>

On Tue, Jun 3, 2008 at 12:24 AM, Peter Karlsson <peter@softwolves.pp.se> wrote:
> Hi!
>
> As I continue to introduce Git at my workplace, I got the question on
> how to integrate external diff tools with Git. I figured out a way to
> get it to work with the command-line "git-diff", by setting
> GIT_EXTERNAL_DIFF and hacking together a small batch file (yeah, this
> is on Windows) that opens the diff in the viewer. For myself, I would
> like to use tkdiff, whereas the rest of the team is used to another
> side-by-side diff viewer.

Have you taken a look at ugit?

http://repo.or.cz/w/ugit.git
(requires the latest GitPython http://gitorious.org/projects/git-python/)

It can launch external diff tools.  It also has a very fine diff gui.
You can either select the entire diff hunk or, if you need to be more
precise, drill down to specific lines from a diff.

If the built-in diff selection doesn't suffice just right-click in the
modified files section where there's an option to send the diff to a
diff editor.  You can define that to be tkdiff, xxdiff, etc.

-- 
 David

  reply	other threads:[~2008-06-03 10:57 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-03  7:24 External diff viewer and stage/merge tool and git-gui? Peter Karlsson
2008-06-03 10:56 ` David Aguilar [this message]
2008-06-03 13:40   ` Peter Karlsson

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=402731c90806030356r1ea4317vef40b6449f4fca16@mail.gmail.com \
    --to=davvid@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=peter@softwolves.pp.se \
    /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).