forked from mirrors/jj
4221c7cf5c
I think the idea behind `handle_ancestor_ops()` was to let our backend at Google delegate the work to the server, which could then avoid walking ancestors. However, we're now thinking that we're going to make our server resolve divergent operations on its own instead, so the client will never see more than one op head, unless it manually creates the second op head itself (e.g. because the user ran two concurrent commands). In those cases it should be fine to do the walk. So let's simplify the trait by removing the function. |
||
---|---|---|
.. | ||
benches | ||
gen-protos | ||
src | ||
tests | ||
testutils | ||
Cargo.toml | ||
LICENSE |