Update Git to v2.20.0.vfs.1.1

[derrickstolee]

Includes v2.20.0.windows.1.

It also disables reset.quiet (correctness issue) and rebase.useBuiltin (performance issue).

[derrickstolee]

@kewillford The functional tests are breaking on things like 'reset' and 'status', and the biggest change in gvfs-2.19.1 since the last time we had functional tests succeeding with a 2.20 release candidate is the post-index-changed hook. Could you take a look at these build failures?

[kewillford]

@derrickstolee @benpeart was there some change to the output of reset --mixed to not display the files that are updated/deleted. Maybe we aren't setting a flag in the control repo that we are using in VFSForGit? I will dig in and see what I can find.

[derrickstolee]

@kewillford @benpeart @jrbriggs It appears that the "reset.quiet" setting doesn't work well in our setting. I tried setting it to true in our control repo, but that wasn't enough. Disabling it in our processes made the functional tests pass.

My guess is that the index-changed hook merged cleanly with the reset quiet code in 2.20.0, but that merge introduced a different behavior than the hook expects. For now, I'll clean up this PR to only update the Git version and remove the "reset.quiet" setting and we can work to fix the integration in a follow-up PR.

[derrickstolee]

@benpeart The latest functional test failures all have a message like this:

Extra: fatal: 'git gc' is not supported on a GVFS repo

This is because I forgot to include your command-canceling PR in the previous builds.

Turns out: we are calling git gc --auto from a lot of commands, and that is being halted by that patch.

I'm tempted to pull the change out of the v2.20.0 PR and work to reapply the change directly to that branch. We can then find the best way to halt auto-GC in a VFS for Git repo.

[benpeart]

I'm tempted to pull the change out of the v2.20.0 PR and work to reapply the change directly to that branch. We can then find the best way to halt auto-GC in a VFS for Git repo.

Yes, please pull this patch out of 2.20.0 - I'll go back and figure out best to handle the automatic 'git gc --auto' commands (which will fail silently later as we turn off auto GC in VFSForGIT repos).

My bad - I hadn't merged the PR to switch VFSForGIT to use the new version of git yet and didn't expect it to get pulled into 2.20.0 before I'd had a chance to run the functional tests.

[kewillford]

Do you know what is running the gc --auto or why it is running? We set { "gc.auto", "0" }, in the config for the repo which I though should be disabling it.

[benpeart]

Do you know what is running the gc --auto or why it is running? We set { "gc.auto", "0" }, in the config for the repo which I though should be disabling it.

Several git commands spawn "gc --auto" themselves (am, commit, fetch, merge, rebase, etc). I've updated the patch in git to check for --auto and will only die if the config setting 'gc.auto' isn't "0" (ie turned off).

[derrickstolee]

The latest push disables the builtin rebase. This is to check the performance results. It may cause a failure in the functional tests due to different warning/error messages.