Note: I'm passing this report from an internal user. I've recommended that they use git reset --hard as a way that should avoid the current regression as well as communicating to Git the full expectation of what is going on, but this performance regression should be avoided. Unfortunately, this also means the issue fixed by #658 is not fully fixed.
Setup
microsoft/git
are you using? Is it 32-bit or 64-bit?Are you using Scalar or VFS for Git?
VFS for Git
If VFS for Git, then what version? (latest)
Details
This used to be fast, but now is slow.