Scenario: The user passes --ignore a/foo/bar, which exists, but during the comparison, a/foo errors out. In this case, it will report b/foo as missing. Currently, this means it will also report b/foo/bar as missing even though the semantics of --ignore in compare() mean "ignore this side, as well as the equivalent path on the other side."
We probably want to keep the same semantics as in compare(), since the user might be trying to ignore a really big directory that exists on both sides, and a transient error on one side shouldn't cause that whole big directory on the other side to be reported.
See #36 for defining the complete semantics.
Scenario: The user passes
--ignore a/foo/bar, which exists, but during the comparison,a/fooerrors out. In this case, it will reportb/fooas missing. Currently, this means it will also reportb/foo/baras missing even though the semantics of--ignoreincompare()mean "ignore this side, as well as the equivalent path on the other side."We probably want to keep the same semantics as in compare(), since the user might be trying to ignore a really big directory that exists on both sides, and a transient error on one side shouldn't cause that whole big directory on the other side to be reported.
See #36 for defining the complete semantics.