From: Mircea Bardac <dev@mircea.bardac.net>
To: git@vger.kernel.org
Subject: possible 'git cp'/how does git detect copies
Date: Fri, 27 Jun 2008 13:40:22 +0100 [thread overview]
Message-ID: <4864DFB6.3050204@mircea.bardac.net> (raw)
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.
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.
[1] http://kerneltrap.org/mailarchive/git/2008/2/3/705424
Many thanks,
Mircea
--
http://mircea.bardac.net
next reply other threads:[~2008-06-27 12:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-27 12:40 Mircea Bardac [this message]
2008-06-27 12:57 ` possible 'git cp'/how does git detect copies 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
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=4864DFB6.3050204@mircea.bardac.net \
--to=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.