Shuqi Liang <cheskaqiqi@xxxxxxxxx> writes: > +test_expect_success 'diff-files with pathspec outside sparse definition' ' > + init_repos && > + > + test_sparse_match test_must_fail git diff-files folder2/a && In "sparse" directories at this point of test, "folder2" is outside the cone(s) of interest and is not instantiated. The reason why the command fails is because the command line parsing that is generic to all users of the revision machinery requires you to have a disambiguating double-dash before such a pathspec that tries to match a path that does not exist in the working tree and is not specific to "diff-files". I wonder how interesting and useful this test is. Without accompanying test that uses disambiguating double-dash properly, e.g. "git diff-files -- folder2", I doubt it is very much useful. > + write_script edit-contents <<-\EOF && > + echo text >>"$1" > + EOF > + > + # Add file to the index but outside of cone for sparse-checkout cases. > + # Add file to the index without sparse-checkout cases to ensure all have > + # same output. > + run_on_all mkdir -p folder1 && > + run_on_all cp a folder1/a && Now, "folder1" also has not been instantiated in sparse ones while the full one of course has it, so "-p" in "mkdir -p" makes sense. After these commands, all three will share the same "folder1/a". > + # file present on-disk without modifications > + # use `--stat` to ignore file creation time differences in > + # unrefreshed index > + test_all_match git diff-files --stat && > + test_all_match git diff-files --stat folder1/a && > + test_all_match git diff-files --stat "folder*/a" && Because in all three repositories, "folder1/a" exists in the working tree, the "you need to disambiguate" error like the first test (whose utility I questioned) would not trigger. What does this demonstrate, though? That instantiating a file on the working tree, even outside the cone(s) of interest in a sparsely checked out working tree, makes it part of the interesting set automatically? As there is no difference between the indexed contents and what is in the working tree, we cannot tell from this test if that is the case (not a complaint, just an observation). But ... > + # file present on-disk with modifications > + run_on_all ../edit-contents folder1/a && > + test_all_match git diff-files && > + test_all_match git diff-files folder1/a && > + test_all_match git diff-files "folder*/a" ... it is shown by doing the same test with modified contents? For consistency with the earlier "the same contents" test, we should use "--stat" here, too. Or even "--stat -p". Alternatively, we could refresh the index before running diff-files (here and also before the earlier "the same contents" test), I guess. > +' > + > test_done Thanks.
