Re: possible 'git cp'/how does git detect copies

[Pierre Habouzit <madcoder@debian.org>]

[-- Attachment #1: Type: text/plain, Size: 1495 bytes --]

On Fri, Jun 27, 2008 at 12:40:22PM +0000, Mircea Bardac wrote:
> I was looking today at duplicating a file but, I soon realized that there 
> is no 'git cp' command (this was the "deductive approach to git 
> commands", starting from git mv/rm/...). How does "git diff -C" detect 
> 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.

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

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

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

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

-- 
·O·  Pierre Habouzit
··O                                                madcoder@debian.org
OOO                                                http://www.madism.org

[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]