ConfigStep: disable status.submoduleSummary when using GVFS protocol #383
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
A VFS for Git user noticed extremely slow "git status" times, and the
root cause was that they had set status.submoduleSummary=true in their
global config. This causes two "git submodule" subprocesses, which are
very slow. The GVFS protocol does not allow submodules, so disable the
setting when using that protocol.
I investigating fixing this in Git proper, but there is no efficient
way to detect that we can ignore this setting since there could be
an untracked submodule.