Martin von Zweigbergk 82883e648d conflicts: move describe_conflict() etc. onto Conflict ... Before we had `conflicts::Conflict`, most of these functions took a `backend::Conflict`. I think I didn't want to pollute the `backend` module with this kind of logic, trying to keep it focused on storage. Now that we have the type in `conflicts`, however, I think it makes sense to move these functions onto it.		2023-06-19 07:05:02 +02:00
..
test_bad_locking.rs
test_commit_builder.rs
test_commit_concurrent.rs
test_conflicts.rs	conflicts: move describe_conflict() etc. onto Conflict	2023-06-19 07:05:02 +02:00
test_default_revset_graph_iterator.rs
test_diff_summary.rs
test_git.rs
test_id_prefix.rs
test_index.rs	index: turn CompositeIndex::walk_revs() into position-based API	2023-06-19 13:41:43 +09:00
test_init.rs
test_load_repo.rs
test_merge_trees.rs	store: do conversion to/from backend::Conflict	2023-06-04 06:48:34 -07:00
test_mut_repo.rs
test_operations.rs
test_refs.rs
test_revset.rs	revsets: stop jj parsing br as a git_ref refs/heads/br	2023-06-12 14:31:44 -07:00
test_rewrite.rs
test_view.rs
test_working_copy.rs	store: do conversion to/from backend::Conflict	2023-06-04 06:48:34 -07:00
test_working_copy_concurrent.rs
test_working_copy_sparse.rs
test_workspace.rs