We hit a case when a rename DELETED some files that where in P, V and M!

After an investigation, we tracked the problem:
  *  Merge calls "find_filename_changes(between p and m)"
  *  find_filename_changes calls bisect_shortest_path( directOnly )

We think that if we change the find_filename_changes() so bisect_shortest_path gets called with "directOnly=false", it solves all our problems.

But we don't know further consequences from this. We need this problem fixed. drh, as you implemented all this, could you tell us if this is the change to do?

I will attach the patch that removes the directOnly on find_filename_changes.