Martin von Zweigbergk 4e8fbaa210 git: allow conflicts in "HEAD@git" ... Git's HEAD ref is similar to other refs and can logically have conflicts just like the other refs in `git_refs`. As with the other refs, it can happen if you run concurrent commands importing two different updates from Git. So let's treat `git_head` the same as `git_refs` by making it an `Option<RefTarget>`.		2023-01-30 09:05:03 -08:00
..
test_bad_locking.rs
test_commit_builder.rs
test_commit_concurrent.rs	cleanup: update more "checkout" to "working-copy commit" and similar	2023-01-25 11:02:59 -08:00
test_conflicts.rs
test_diff_summary.rs
test_git.rs	git: allow conflicts in "HEAD@git"	2023-01-30 09:05:03 -08:00
test_index.rs
test_init.rs	cleanup: update more "checkout" to "working-copy commit" and similar	2023-01-25 11:02:59 -08:00
test_load_repo.rs
test_merge_trees.rs
test_mut_repo.rs	cleanup: update more "checkout" to "working-copy commit" and similar	2023-01-25 11:02:59 -08:00
test_operations.rs
test_refs.rs
test_revset.rs	git: allow conflicts in "HEAD@git"	2023-01-30 09:05:03 -08:00
test_revset_graph_iterator.rs
test_rewrite.rs
test_view.rs	git: allow conflicts in "HEAD@git"	2023-01-30 09:05:03 -08:00
test_working_copy.rs
test_working_copy_concurrent.rs
test_working_copy_sparse.rs
test_workspace.rs