--- Junio C Hamano wrote:
> Max Pollard writes:
>
> > ... So -C -C is the answer, with --name-status or --stat to
> > actually show the result.
>
> The real "answer" part in that example is not -C -C. Obviously,
> you would need double-C aka --find-copies-harder, because you
> did not change a.txt when creating b.txt, so it is still needed.
>
> But the essential part of the answer is "not giving b.txt as the
> pathspec, so that whatever _other_ file that could have been
> copied into it is still visible when the command works".
>
> If you say "git log --name-status -C -C -- b.txt", you would be
> back to square one.
Aha, point taken. In this case, looks like I can do:
$ git log -C -C --full-diff --name-status/--stat/--summary -- b.txt
as Sean has suggested to get the copy information back. Or are you saying that
even with "--full-diff" I can lose copy information in some cases?
MP
____________________________________________________________________________________
Looking for last minute shopping deals?
Find them fast with Yahoo! Search. http://tools.search.yahoo.com/newsearch/category.php?category=shopping
-
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
