Yuya Nishihara 9aa72f6f1d git_backend: add lock to prevent racy change id assignments ... My first attempt was to fix up corrupted index when merging, but it turned out to be not easy because the self side may contain corrupted data. It's also possible that two concurrent commit operations have exactly the same view state (because change id isn't hashed into commit id), and only the table heads diverge. #924		2023-05-20 15:53:23 +09:00
..
test_bad_locking.rs
test_commit_builder.rs	git_backend: return timestamps for what was actually written	2023-05-12 15:20:44 -07:00
test_commit_concurrent.rs
test_conflicts.rs
test_default_revset_graph_iterator.rs	revset: resolve visible heads prior to evaluation	2023-04-10 00:39:58 +09:00
test_diff_summary.rs
test_git.rs	git_backend: add lock to prevent racy change id assignments	2023-05-20 15:53:23 +09:00
test_id_prefix.rs	id_prefix: remove repo field from IdPrefixContext	2023-05-11 23:41:24 -07:00
test_index.rs	index: remove entry_by_id() from trait	2023-04-18 18:32:23 -07:00
test_init.rs	backend: replace git_repo() by as_any()	2023-05-12 08:05:09 -07:00
test_load_repo.rs
test_merge_trees.rs
test_mut_repo.rs
test_operations.rs
test_refs.rs
test_revset.rs	git_backend: return timestamps for what was actually written	2023-05-12 15:20:44 -07:00
test_rewrite.rs
test_view.rs
test_working_copy.rs	working_copy: introduce snapshot progress callback	2023-05-06 11:07:46 -07:00
test_working_copy_concurrent.rs	working_copy: introduce snapshot progress callback	2023-05-06 11:07:46 -07:00
test_working_copy_sparse.rs	working_copy: introduce snapshot progress callback	2023-05-06 11:07:46 -07:00
test_workspace.rs