From: Andy Parkins <andyparkins@gmail.com>
To: git@vger.kernel.org
Cc: Jakub Narebski <jnareb@gmail.com>
Subject: Re: Rename detection at git log
Date: Mon, 20 Nov 2006 12:59:12 +0100 [thread overview]
Message-ID: <200611201159.16596.andyparkins@gmail.com> (raw)
In-Reply-To: <ejs2lp$2r4$1@sea.gmane.org>
On Monday 2006 November 20 11:15, Jakub Narebski wrote:
> I'm not sure about this. You usually both do pure renames (to reorganize
> files, to give file a better name) and renames with modification, but
> I don't think that copy without modification is very common. Usually you
> copy a file because you take one file as template for the other, or you
> split file, or you join files into one file.
Exactly - unfortunately it's the /source/ that has to be modified to be
included in the potential list. Who copies a file then modifies the
original? The copy is by definition already one of the modified files.
"For performance reasons, by default, -C option finds copies only if the
original file of the copy was modified in the same changeset. This flag makes"
Your points about copy-and-change accepted. Hash comparison is not
sufficient.
Andy
--
Dr Andy Parkins, M Eng (hons), MIEE
next prev parent reply other threads:[~2006-11-20 11:59 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-20 5:57 Rename detection at git log Alexander Litvinov
2006-11-20 9:50 ` Andy Parkins
2006-11-20 10:07 ` Junio C Hamano
2006-11-20 10:11 ` Jakub Narebski
2006-11-20 10:22 ` Andy Parkins
2006-11-20 10:48 ` Junio C Hamano
2006-11-20 11:01 ` Andy Parkins
2006-11-20 11:15 ` Jakub Narebski
2006-11-20 11:32 ` Junio C Hamano
2006-11-20 11:59 ` Andy Parkins [this message]
2006-11-20 11:28 ` Junio C Hamano
2006-11-20 12:16 ` Andy Parkins
2006-11-20 11:33 ` Alexander Litvinov
2006-11-20 10:06 ` Alex Riesen
2006-11-20 10:23 ` Andy Parkins
2006-11-20 10:51 ` Junio C Hamano
2006-11-20 11:17 ` Andy Parkins
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=200611201159.16596.andyparkins@gmail.com \
--to=andyparkins@gmail.com \
--cc=git@vger.kernel.org \
--cc=jnareb@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 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.