Re: [PATCH 2/5] scalar: use index.skipHash=true for performance
- From
Junio C Hamano <gitster@pobox.com>
- Date
- Nov 26, 2025, 23:57 UTC
- Message-ID
- <xmqqldjsl53m.fsf@gitster.g>
- In-Reply-To
- <1c51dbb81485920e9faf336ffbda9d9258e7dfe1.1764195516.git.gitgitgadget@gmail.com>
"Derrick Stolee via GitGitGadget" <gitgitgadget@gmail.com> writes:
Show 12 quoted lines
> diff --git a/t/t9210-scalar.sh b/t/t9210-scalar.sh > index 43c210a23d..91d5964b73 100755 > --- a/t/t9210-scalar.sh > +++ b/t/t9210-scalar.sh > @@ -246,6 +246,11 @@ test_expect_success 'scalar reconfigure --all with includeIf.onbranch' ' > ' > > test_expect_success 'scalar reconfigure --all with detached HEADs' ' > + # This test demonstrates an issue with index.skipHash=true and > + # this test variable for the split index. Disable the test variable. > + GIT_TEST_SPLIT_INDEX= && > + export GIT_TEST_SPLIT_INDEX &&
Interesting. I would have expected to see a simple "sane_unset", instead of exporting an empty setting explicitly.
> repos="two three four" && > for num in $repos > do