From: Jeff King <peff@peff.net>
Date: Thu, 05 May 2011 20:01:30 GMT
Subject: Re: How to fork a file (git cp ?)
Message-ID: <20110505200130.GB1770@sigill.intra.peff.net>
In-Reply-To: <4DC2FB0A.2090100@aldan.algebra.com>

On Thu, May 05, 2011 at 03:31:22PM -0400, Mikhail T. 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...

I think "git log --follow" will do what you want; it uses
FIND_COPIES_HARDER.

> On 05.05.2011 14:02, Piotr Krukowiecki wrote:
> >Maybe Mikhail wanted to say that if there's a git-mv as a shortcut for
> >   "cp old new ; rm old; add new"
> git-mv preserves the old's change-history in new, so it is more than
> the above, is not it?

No. The renames are detected at the time of viewing, not at the time of
commit.

-Peff