Yuya Nishihara 51520bc87b working_copy: don't follow symlinks while creating parent directories ... Otherwise a file could be created out of the working copy directory. This only works for untracked symlinks and sequentially "added" symlinks and files. For "removed" and "modified" entries, the parent directories are considered valid and fs::remove_file() will be called. This also doesn't prevent race conditions caused by concurrent checkouts. New create_parent_dirs() would be slightly slower than the original because it traverses directories from the root whereas fs::create_dir_all() does that from the leaf and exits when reached to a directory.		2022-08-17 13:22:51 +09:00
..
test_bad_locking.rs
test_commit_builder.rs
test_commit_concurrent.rs
test_conflicts.rs
test_diff_summary.rs
test_git.rs
test_index.rs
test_init.rs
test_load_repo.rs
test_merge_trees.rs
test_mut_repo.rs
test_operations.rs
test_refs.rs
test_revset.rs
test_revset_graph_iterator.rs
test_rewrite.rs
test_view.rs
test_working_copy.rs	working_copy: don't follow symlinks while creating parent directories	2022-08-17 13:22:51 +09:00
test_working_copy_concurrent.rs
test_working_copy_sparse.rs
test_workspace.rs