Git development
 help / color / mirror / Atom feed
From: Johannes Sixt <j.sixt@viscovery.net>
To: Mircea Bardac <dev@mircea.bardac.net>
Cc: git@vger.kernel.org
Subject: Re: possible 'git cp'/how does git detect copies
Date: Fri, 27 Jun 2008 15:05:18 +0200	[thread overview]
Message-ID: <4864E58E.4090000@viscovery.net> (raw)
In-Reply-To: <4864DFB6.3050204@mircea.bardac.net>

Mircea Bardac schrieb:
> 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)?
> 
> 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.
> 
> This is all with 1.5.6.1.
> 
> I am probably missing something here... but I can't produce an example
> of copied contents that actually works. Any hint would be appreciated.

If you modify the original file in the same commit, then you should see
the copy. Otherwise, you can try git diff -C -C aka --find-copies-harder.

-- Hannes

      parent reply	other threads:[~2008-06-27 13:06 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-27 12:40 possible 'git cp'/how does git detect copies Mircea Bardac
2008-06-27 12:57 ` Santi Béjar
2008-06-27 13:16   ` Mircea Bardac
2008-06-27 13:00 ` Pierre Habouzit
2008-06-27 13:09   ` Miklos Vajna
2008-06-27 13:05 ` Johannes Sixt [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4864E58E.4090000@viscovery.net \
    --to=j.sixt@viscovery.net \
    --cc=dev@mircea.bardac.net \
    --cc=git@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox