Re: Bug?: 'git log --find-copies' doesn't match 'git log --follow <rev> -- path/to/file'

From: Alexander Pepper <pepper@inf.fu-berlin.de>
Date: Oct 2, 2011, 15:10 UTC
Message-ID: <67B22035-4B90-4A68-8960-DDB58F640CD9@inf.fu-berlin.de>
In-Reply-To: <20110930213841.GA9384@sigill.intra.peff.net>

Am 30.09.2011 um 23:38 schrieb Jeff King:

Show 15 quoted lines

> On Fri, Sep 30, 2011 at 05:32:38PM +0200, Alexander Pepper wrote:
> 
>> So git log with copy and rename detection on (--find-copies) tells me,
>> that the file StopClusterException.java is copied to
>> ClusterOperation.java. But If I ask git log for that specific file
>> with --follow git claims a copy from Immutable.java to
>> ClusterOperation.java!
> 
> I think that --follow uses --find-copies-harder. Did you try:
> 
>  git log --numstat --find-copies-harder dd4e90f9
> 
> ? Does it find Immutable.java as the source?
> 
> -Peff

Using 'git log --numstat --find-copies-harder dd4e90f9' yields "immutable.java" as you expected:

$ git log --numstat --find-copies-harder dd4e90f9 [...] 6 10 src/java/voldemort/annotations/concurrency/Immutable.java => contrib/ec2-testing/src/java/voldemort/utils/ClusterOperation.java

So is there a way to tell --follow to only use --find-copies instead of --find-copies harder? And what is the advantage of using "--find-copies-harder" over "--find-copies"?

Greetings from Berlin Alex

-- 
Alexander Pepper
pepper@inf.fu-berlin.de