Elijah Newren <newren@xxxxxxxxx> writes: > This is not true. If src/main.c is 99% similar to src/foo.c, and is > 0% similar to the src/main.c in the new commit, we match the old > src/main.c to the new src/main.c despite being far more similar > src/foo.c. Unless break detection is turned on, we do not allow > content similarity to trump (full) filename equality. Absolutely. And we are talking about a new optimization that kicks in only when there is no break or no copy detection going on, no?