From: Pete Harlan <pgit@pcharlan.com>
Date: Sun, 08 May 2011 19:40:56 GMT
Subject: Re: How to fork a file (git cp ?)
Message-ID: <4DC6F1C8.8040007@pcharlan.com>
In-Reply-To: <BANLkTikE8aMh6RUDzrh=SuOxvKxuPShQhQ@mail.gmail.com>

On 5/5/2011 1:01 PM, Piotr Krukowiecki wrote:
> On Thu, May 5, 2011 at 9:31 PM, Mikhail T.<mi+thun@aldan.algebra.com>  wrote:
>> On 04.05.2011 22:14, Junio C Hamano wrote:
>>>
>>> I think that is what exactly "blame -C -C" gives you.
>>
>> For that to be useful, one has to suspect, the file was derived by copying
>> something else... Simple "git log" will not suggest that -- unless the
>> commit message, that adds the new copy of a file points to it...
>
> Maybe it should be the default (performance issues?)

...

> BTW, I don't understand why 'status' shows renames but not copies:

Rename detection compares new files against deleted files.  Copy 
detection compares new files against every file in the tree, which is 
usually much more costly.

--Pete