On Fri, 26 Oct 2007, Linus Torvalds wrote: > > Works For Me(tm), although this isn't all that obviously testable (ie I > should find a test that is border-line, and triggers the rename detection > limits, but then has enough exact renames that the rename detection array > goes away). Actually, I just tested it. I used that same 100,000 file thing, but added one more (larger) file, and did another commit that moved the 100,000 files exactly, and the one larger file with a small change. The code before this patch (but with my linear-time rename changes) would find the 100,000 exact renames, but would *not* find the one that had a small change, because it would hit the rename limit, and wouldn't even try. With these two patches in place, it finds all the exact renames, and once it has done that, the resulting rename array is small enough (one single unknown target remaining, even if there are 100,001 possible source files) that it doesn't trigger the rename limit, and it now finds the remaining non-exact rename too. So it not only looked obvious, it seems to work too. Linus - To unsubscribe from this list: 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
