From: Junio C Hamano <gitster@pobox•com>
To: Jeff King <peff@peff•net>
Cc: Bryan Turner <bturner@atlassian•com>,
Pol Online <info@pol-online•net>, Git Users <git@vger•kernel.org>
Subject: Re: git status / git diff -C not detecting file copy
Date: Wed, 03 Dec 2014 08:03:18 -0800 [thread overview]
Message-ID: <xmqq61dslnzt.fsf@gitster.dls.corp.google.com> (raw)
In-Reply-To: <20141202215013.GB25338@peff.net> (Jeff King's message of "Tue, 2 Dec 2014 16:50:13 -0500")
Jeff King <peff@peff•net> writes:
> ... I'd consider trying to match diff.renames instead,
> which takes false/true/copies for its three levels. It may make sense to
> teach both places "copies-harder" or something similar, for
> completeness.
Yeah, I think that is a very sensible thing to do.
prev parent reply other threads:[~2014-12-03 16:03 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-30 0:35 git status / git diff -C not detecting file copy Pol Online
2014-11-30 1:03 ` Bryan Turner
2014-11-30 1:30 ` Pol Online
2014-11-30 1:54 ` Bryan Turner
2014-12-02 6:55 ` Jeff King
2014-12-02 14:15 ` Pol Online
2014-12-02 17:57 ` Junio C Hamano
2014-12-02 20:09 ` Jeff King
2014-12-03 16:01 ` Junio C Hamano
2014-12-02 21:40 ` Bryan Turner
2014-12-02 21:50 ` Jeff King
2014-12-03 16:03 ` Junio C Hamano [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=xmqq61dslnzt.fsf@gitster.dls.corp.google.com \
--to=gitster@pobox$(echo .)com \
--cc=bturner@atlassian$(echo .)com \
--cc=git@vger$(echo .)kernel.org \
--cc=info@pol-online$(echo .)net \
--cc=peff@peff$(echo .)net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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