Martin Waitz <tali@xxxxxxxxxxxxxx> writes: > The reason for that is that is_exact_match (in diffcore-rename.c) maps > both the source and destination file into memory and then compares them > byte for byte. This is a little bit too much for my little machine. > > When I remove the content comparation and only leave the sha1 > comparision, then my renames are correctly found in a second. But > unluckily, some other renames in the testcases are not correctly > handled any more. > > So is there an easy solution? Why is the content comparision in > is_exact_match needed? Because your working tree can be out of sync with respect to what's in the index, in which case we cannot trust the sha1 while running diff-index (without --cached flag). git-update-index --refresh before doing anything might help. - : send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html