On Fri, Jun 27, 2008 at 12:40:22PM +0000, Mircea Bardac wrote:
quoted text
> I was looking today at duplicating a file but, I soon realized that there=
=20
quoted text
> is no 'git cp' command (this was the "deductive approach to git=20
> commands", starting from git mv/rm/...). How does "git diff -C" detect=20
> copies (-C is used for this, according to the documentation)?

  By comparing if files (blobs) are alike. It has some heuristics to
guess which files have good changes to be copies or renames of each
others. But it recomputes the information each time.

quoted text
> On a very simple test, I couldn't see this working. I just copied one=20
> file, added it, committed the change, ran "git diff -C HEAD^!". There is=
=20
quoted text
> no place saying that it's contents is copied from some other file (both=
=20
quoted text
> files are in the repository now).
>=20
> "git blame -C new_copied_file" also doesn't show the commits for the=20
> original file.

  You probably want to use -C -C -M actually.

quoted text
> I found this older thread [1] on "git cp" but the discussion appears to=
=20
quoted text
> have stalled at some point. If there is indeed no use of a "git cp"=20
> command, I would like at least some info on how content copies are being=
=20
quoted text
> detected, since I haven't seen this working.

  If you really need it, you can and an alias alias.cp=3D!cp and be done
with it ;P

--=20
=C2=B7O=C2=B7  Pierre Habouzit
=C2=B7=C2=B7O                                                madcoder@debia=
n.org
OOO                                                http://www.madism.org