git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Nazri Ramliy" <ayiehere@gmail.com>
To: "René Scharfe" <rene.scharfe@lsrfire.ath.cx>
Cc: "Junio C Hamano" <gitster@pobox.com>, git@vger.kernel.org
Subject: Re: [PATCH (Eek!)] git diff does not honor --no-ext-diff
Date: Wed, 26 Nov 2008 18:01:27 +0800	[thread overview]
Message-ID: <544dda350811260201t66a58c9av3f390d6f314ffa05@mail.gmail.com> (raw)
In-Reply-To: <492D01D1.7020702@lsrfire.ath.cx>

On Wed, Nov 26, 2008 at 3:59 PM, René Scharfe
<rene.scharfe@lsrfire.ath.cx> wrote:
> Junio C Hamano schrieb:
>>
>> Wouldn't this be a better patch?
>
> Yes.  And feel free to squash in the following. :)
>

Good! So the Eek! part is not really necessary.

Now I can trigger the external diff whenever I say so via GIT_EXTERNAL_DIFF.

Thanks.

Nazri.

      reply	other threads:[~2008-11-26 10:02 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-26  7:12 [PATCH (Eek!)] git diff does not honor --no-ext-diff Nazri Ramliy
2008-11-26  7:52 ` Junio C Hamano
2008-11-26  7:59   ` René Scharfe
2008-11-26 10:01     ` Nazri Ramliy [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=544dda350811260201t66a58c9av3f390d6f314ffa05@mail.gmail.com \
    --to=ayiehere@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=rene.scharfe@lsrfire.ath.cx \
    /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).