Re: Rename detection at git log
- From
- Andy Parkins <andyparkins@gmail.com>
- Date
- Nov 20, 2006, 11:59 UTC
- Message-ID
- <200611201159.16596.andyparkins@gmail.com>
- In-Reply-To
- <ejs2lp$2r4$1@sea.gmane.org>
On Monday 2006 November 20 11:15, Jakub Narebski wrote:
Show 5 quoted lines
> 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