summaryrefslogtreecommitdiffstats
path: root/contrib/persistent-https
diff options
context:
space:
mode:
authorDerrick Stolee <stolee@gmail.com>2025-12-12 15:15:25 +0000
committerJunio C Hamano <gitster@pobox.com>2025-12-13 08:43:27 +0900
commit05f28e4b3cc1f873e510e5692b70290c515abb98 (patch)
treecfd5ad891e132accad62f25b6c9a87b9a056a5a2 /contrib/persistent-https
parent48695fcde51e10d6d6e72653fb94b5fd339cd6e6 (diff)
downloadgit-05f28e4b3cc1f873e510e5692b70290c515abb98.tar.gz
git-05f28e4b3cc1f873e510e5692b70290c515abb98.zip
scalar: use index.skipHash=true for performance
The index.skipHash config option has been set to 'false' by Scalar since 4933152cbb (scalar: enable path-walk during push via config, 2025-05-16) but that commit message is trying to communicate the exact opposite: that the 'true' value is what we want instead. This means that we've been disabling this performance benefit for Scalar repos unintentionally. Fix this issue before we add justification for the config options set in this list. Oddly, enabling index.skipHash causes a test issue during 'test_commit' in one of the Scalar tests when GIT_TEST_SPLIT_INDEX is enabled (as caught by the linux-test-vars build). I'm fixing the test by disabling the environment variable, but the issue should be resolved in a series focused on the split index. Signed-off-by: Derrick Stolee <stolee@gmail.com> Signed-off-by: Junio C Hamano <gitster@pobox.com>
Diffstat (limited to 'contrib/persistent-https')
0 files changed, 0 insertions, 0 deletions