From: Tim Henigan <tim.henigan@gmail.com>
To: Junio C Hamano <gitster@pobox.com>, David Aguilar <davvid@gmail.com>
Cc: git@vger.kernel.org, ramsay@ramsay1.demon.co.uk
Subject: Re: [PATCH 8/9 v13] difftool: teach difftool to handle directory diffs
Date: Thu, 19 Apr 2012 13:11:00 -0400 [thread overview]
Message-ID: <CAFouetg6T1pgAiTfyAeSxseR-k_omsZDfqv8X8AifekwPLoE2g@mail.gmail.com> (raw)
In-Reply-To: <7v8vhsltk3.fsf@alter.siamese.dyndns.org>
On Wed, Apr 18, 2012 at 3:38 PM, Junio C Hamano <gitster@pobox.com> wrote:
> Tim Henigan <tim.henigan@gmail.com> writes:
>
>> 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.
Adding '--no-renames' has no effect if the user specifies '-C -C' or
'--find-copies-harder'. Is protecting for these cases too paranoid?
Also, the '--cc' option for viewing merge diffs is not affected by
'--no-renames'.
I have a revised patch that prunes out all of the above and warns the
user when it does so [1].
However, it also prunes them when difftool is called in serial diff
mode (i.e. non --dir-diff). Before, if 'difftool
--find-[renames|copies]' was called it would open the external tool to
compare the two files, but the original file name was used for both
sides of the diff.
This seems confusing, but I don't know if people rely on that
behavior. If we need to keep that behavior in the serial diff mode, I
will need to modify the patch again to only prune the options in
directory diff mode.
[1]: https://github.com/thenigan/git/commit/c3479940a36f3c7c8fe360bc244303b125f711ff
next prev parent reply other threads:[~2012-04-19 17:11 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
2012-04-19 17:11 ` Tim Henigan [this message]
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=CAFouetg6T1pgAiTfyAeSxseR-k_omsZDfqv8X8AifekwPLoE2g@mail.gmail.com \
--to=tim.henigan@gmail.com \
--cc=davvid@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=ramsay@ramsay1.demon.co.uk \
/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).