Skip to content

Conversation

@derrickstolee
Copy link
Contributor

@derrickstolee derrickstolee commented Jul 10, 2020

See microsoft/git#283.

The new logic around core.repositoryFormatVersion and extensions.* config options causes problems in Scalar due to our use of sparse-checkout. This is resolved by some upstream fixes and some more careful config here.

@derrickstolee derrickstolee force-pushed the vfs-2.28.0 branch 3 times, most recently from a6c401e to 044b9ab Compare July 13, 2020 14:50
@derrickstolee derrickstolee force-pushed the vfs-2.28.0 branch 2 times, most recently from 3c14c90 to 2aa290b Compare July 27, 2020 18:16
Signed-off-by: Derrick Stolee <dstolee@microsoft.com>
In Git 2.28.0, the code around extensions changed to not allow the
extensions at all if the repository format version was not increased.
Since the sparse-checkout builtin uses worktree config, we need to
increase this setting.

Signed-off-by: Derrick Stolee <dstolee@microsoft.com>
Signed-off-by: Derrick Stolee <dstolee@microsoft.com>
Some subclasses of GitRepoTests override CreateEnlistment so they can do
extra steps after the base class creates the repo. However, those steps
happen between the base CreateEnlistment() and the rest of the TestSetup
code.

This started failing with the v2.28.0 upgrade because 'git status'
started reporting new info about sparse-checkouts.

Move the sparse-checkout setup code into CreateEnlistment() to stop
failures.

Signed-off-by: Derrick Stolee <dstolee@microsoft.com>
@derrickstolee derrickstolee changed the title [PR Build] Update Git to v2.28.0 Update Git to v2.28.0 Jul 28, 2020
@derrickstolee derrickstolee marked this pull request as ready for review July 28, 2020 11:45
@derrickstolee derrickstolee merged commit 97be7c0 into microsoft:main Jul 28, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants