Taylor Blau wrote: > On Thu, Sep 30, 2021 at 02:50:56PM +0000, Victoria Dye via GitGitGadget wrote: >> From: Victoria Dye <vdye@xxxxxxxxxx> >> >> In anticipation of multiple commands being fully integrated with sparse >> index, update the test for index expand and collapse for non-sparse index >> integrated commands to use `mv`. >> >> Signed-off-by: Victoria Dye <vdye@xxxxxxxxxx> >> --- >> t/t1092-sparse-checkout-compatibility.sh | 2 +- >> 1 file changed, 1 insertion(+), 1 deletion(-) >> >> diff --git a/t/t1092-sparse-checkout-compatibility.sh b/t/t1092-sparse-checkout-compatibility.sh >> index c5977152661..aed8683e629 100755 >> --- a/t/t1092-sparse-checkout-compatibility.sh >> +++ b/t/t1092-sparse-checkout-compatibility.sh >> @@ -642,7 +642,7 @@ test_expect_success 'sparse-index is expanded and converted back' ' >> init_repos && >> >> GIT_TRACE2_EVENT="$(pwd)/trace2.txt" GIT_TRACE2_EVENT_NESTING=10 \ >> - git -C sparse-index -c core.fsmonitor="" reset --hard && >> + git -C sparse-index -c core.fsmonitor="" mv a b && > > Double-checking my understanding as somebody who is not so familiar with > t1092: this test is to ensure that commands which don't yet understand > the sparse index can temporarily expand it in order to do their work? Exactly - if a command doesn't explicitly enable use of the sparse index by setting `command_requires_full_index` to 0, the index is expanded if/when it is first read during the command's execution and collapsed if/when it is written to disk. This test makes sure that mechanism works as intended. -Victoria
