From: Jakub Narebski <jnareb@gmail.com>
To: Evgeny <evgeny.zislis@gmail.com>
Cc: git@vger.kernel.org, tytso@mit.edu
Subject: Re: git mergetool
Date: Sat, 17 May 2008 13:21:10 -0700 (PDT) [thread overview]
Message-ID: <m3tzgw4r7w.fsf@localhost.localdomain> (raw)
In-Reply-To: <b6840c770805171021g63df7d0dm4532655ed49209bc@mail.gmail.com>
Evgeny <evgeny.zislis@gmail.com> writes:
> Background:
> I am trying to use a custom mergetool with git.
> P4Merge from http://www.perforce.com/perforce/products/merge.html
>
> The documentation explains that environment variables
> $BASE, $LOCAL, $REMOTE, $MERGED
> are set for the invocation of the mergetool command.
>
> Problem:
> I wrote a wrapper for P4Merge, and I check for these environment
> variables - but they are not there. After a closer inspection
> of git-mergetool I see that infact these variables are not being
> sent to the external command at all, and are just in the context
> of the git-mergetool script.
>From what I know of git-mergetool, you can use one of the predefined
merge tools: kdiff3, tkdiff, meld, xxdiff, emerge, vimdiff, gvimdiff,
ecmerge, and opendiff (optionally providing path to the tool)
To add support for P4Merge you would have either modify
git-mergetool.sh (and, optionally, send a patch to git mailing list),
or make use of `mergetool.<tool>.cmd` configuration option.
Unfortunately there is no example...
--
Jakub Narebski
Poland
ShadeHawk on #git
next prev parent reply other threads:[~2008-05-17 20:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-17 17:21 git mergetool Evgeny
2008-05-17 20:21 ` Jakub Narebski [this message]
2008-05-17 20:47 ` David Aguilar
2008-05-17 21:32 ` Evgeny
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=m3tzgw4r7w.fsf@localhost.localdomain \
--to=jnareb@gmail.com \
--cc=evgeny.zislis@gmail.com \
--cc=git@vger.kernel.org \
--cc=tytso@mit.edu \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.