From: Junio C Hamano <gitster@pobox.com>
To: Pete Harlan <pgit@pcharlan.com>
Cc: Piotr Krukowiecki <piotr.krukowiecki@gmail.com>,
"Mikhail T." <mi+thun@aldan.algebra.com>,
Johannes Sixt <j6t@kdbg.org>,
git@vger.kernel.org
Subject: Re: How to fork a file (git cp ?)
Date: Sun, 08 May 2011 13:03:03 -0700 [thread overview]
Message-ID: <7vd3jtrmdk.fsf@alter.siamese.dyndns.org> (raw)
In-Reply-To: <4DC6F1C8.8040007@pcharlan.com> (Pete Harlan's message of "Sun, 08 May 2011 12:40:56 -0700")
Pete Harlan <pgit@pcharlan.com> writes:
> Rename detection compares new files against deleted files. Copy
> detection compares new files against every file in the tree, which is
> usually much more costly.
Almost correct. Copy detection usually compares new paths with paths
modified in the same commit. "Every file in the tree" is done only when
you ask to find copies harder.
prev parent reply other threads:[~2011-05-08 20:03 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-04 17:56 How to fork a file (git cp ?) Mikhail T.
2011-05-04 18:16 ` Johannes Sixt
2011-05-04 18:22 ` Johannes Sixt
2011-05-04 19:05 ` Stephen Bash
2011-05-04 19:17 ` Mikhail T.
2011-05-04 20:36 ` Øyvind A. Holm
2011-05-04 21:02 ` Junio C Hamano
2011-05-05 1:58 ` Mikhail T.
2011-05-05 2:14 ` Junio C Hamano
2011-05-05 18:02 ` Piotr Krukowiecki
2011-05-05 18:50 ` Junio C Hamano
2011-05-05 19:27 ` Piotr Krukowiecki
2011-05-05 19:31 ` Mikhail T.
2011-05-05 20:01 ` Jeff King
2011-05-05 20:01 ` Piotr Krukowiecki
2011-05-05 20:06 ` Piotr Krukowiecki
2011-05-05 20:07 ` Jeff King
2011-05-08 19:40 ` Pete Harlan
2011-05-08 20:03 ` Junio C Hamano [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=7vd3jtrmdk.fsf@alter.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=j6t@kdbg.org \
--cc=mi+thun@aldan.algebra.com \
--cc=pgit@pcharlan.com \
--cc=piotr.krukowiecki@gmail.com \
/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;
as well as URLs for NNTP newsgroup(s).