git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Aguilar <davvid@gmail.com>
To: jelly <sinojelly@163.com>
Cc: " Git讨论组(无须订阅) " <git@vger.kernel.org>
Subject: Re: When i run git difftool, git did not use difftool.bc3.cmd,why?
Date: Mon, 8 Aug 2011 04:08:05 -0700	[thread overview]
Message-ID: <EC90E9C8-3745-4E39-9627-945CDC7DD199@gmail.com> (raw)
In-Reply-To: <9c0c497.f7f.131a1fb4855.Coremail.sinojelly@163.com>

On Aug 6, 2011, at 7:03 PM, jelly <sinojelly@163.com> wrote:

>> When i run git difftool, git did not use difftool.bc3.cmd,why?>Even i write a wrong exe file name bcomp1.exe, git still use bcompare.
> I found the reason.
> because bc3 is a special name, git call bcompare internal.change the name bc3, it works fine.

That's right. We have difftool.<tool>.path for this use case.  It lets you redefine the path to the tool (e.g. bcompare).

      reply	other threads:[~2011-08-08 11:13 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-07  1:48 When i run git difftool, git did not use difftool.bc3.cmd,why? jelly
2011-08-07  2:03 ` jelly
2011-08-08 11:08   ` David Aguilar [this message]

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=EC90E9C8-3745-4E39-9627-945CDC7DD199@gmail.com \
    --to=davvid@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=sinojelly@163.com \
    /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).