From: Junio C Hamano <gitster@pobox.com>
To: Tim Henigan <tim.henigan@gmail.com>
Cc: David Aguilar <davvid@gmail.com>,
git@vger.kernel.org, ramsay@ramsay1.demon.co.uk
Subject: Re: [PATCH 8/9 v13] difftool: teach difftool to handle directory diffs
Date: Wed, 18 Apr 2012 12:38:04 -0700 [thread overview]
Message-ID: <7v8vhsltk3.fsf@alter.siamese.dyndns.org> (raw)
In-Reply-To: <CAFouetgWpyUC9SPo_QwpESrbfib7ct111WesKPP14HQ+SqpFaQ@mail.gmail.com> (Tim Henigan's message of "Wed, 18 Apr 2012 14:28:18 -0400")
Tim Henigan <tim.henigan@gmail.com> writes:
> Looking back on it now, I agree that it would have been better to use
> the plumbing commands from the beginning. Changing from the porcelain
> to the plumbing commands will require new logic to parse the diff
> options to figure out which of 'diff-index', 'diff-files' or
> 'diff-tree' should be called. We may also want to add support for
> some specific standard diff options (like '-R').
Yeah, didn't I already suggest that it is the only sane avenue in the long
term to move the whole "populate the two temporary trees" thing down to C
level?
> For now, would you object to an updated patch that simply detects and
> ignores options that change the output of 'git diff --raw'?
As a script that uses 'git diff' is a short-term hack anyway, I think the
most cost effective thing to do is to add '--no-renames' at the end and be
done with it.
next prev parent reply other threads:[~2012-04-18 19:38 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-13 16:36 [PATCH 8/9 v13] difftool: teach difftool to handle directory diffs Tim Henigan
2012-04-15 22:20 ` David Aguilar
2012-04-16 1:01 ` David Aguilar
2012-04-16 8:16 ` David Aguilar
2012-04-17 13:25 ` Tim Henigan
2012-04-18 3:23 ` David Aguilar
2012-04-18 13:13 ` Tim Henigan
2012-04-18 16:25 ` Junio C Hamano
2012-04-18 18:28 ` Tim Henigan
2012-04-18 19:38 ` Junio C Hamano [this message]
2012-04-19 17:11 ` Tim Henigan
2012-04-19 18:49 ` Junio C Hamano
2012-04-20 7:34 ` David Aguilar
2012-04-20 16:58 ` Tim Henigan
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=7v8vhsltk3.fsf@alter.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=davvid@gmail.com \
--cc=git@vger.kernel.org \
--cc=ramsay@ramsay1.demon.co.uk \
--cc=tim.henigan@gmail.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).