git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Peter Karlsson <peter@softwolves.pp.se>
To: Git Mailing List <git@vger.kernel.org>
Subject: External diff viewer and stage/merge tool and git-gui?
Date: Tue, 3 Jun 2008 08:24:28 +0100 (CET)	[thread overview]
Message-ID: <Pine.LNX.4.64.0806030819310.31572@ds9.cixit.se> (raw)

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.

However, I cannot seem to find a way to do it from git-gui, which is
the tool I have taught the rest of the team to use as their primary
interface. Is there a way to view the currently selected difference in
an external diff viewer?


Even better would be a way to allow that external tool to edit what is
to be staged - we are having some problems with version-controlling
sources in some of Borland's tools which have the bad habit of storing
local configuration in the project files, and git-gui's "hunk" picker
cannot be used to pick the relevant changes (we have to set "show less
differences" to the lowest value to get a proper hunk view, and then
git-gui cannot stage anything).

-- 
\\// Peter - http://www.softwolves.pp.se/

             reply	other threads:[~2008-06-03  7:25 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-03  7:24 Peter Karlsson [this message]
2008-06-03 10:56 ` External diff viewer and stage/merge tool and git-gui? David Aguilar
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=Pine.LNX.4.64.0806030819310.31572@ds9.cixit.se \
    --to=peter@softwolves.pp.se \
    --cc=git@vger.kernel.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).