Skip to content

Conversation

@derrickstolee
Copy link

In #836, we implemented custom gvfs..cache-server config options that allow existing enlistments to point specific GVFS Protocol verbs at different cache servers. However, that did not help at clone time.

This change adds ---cache-server-url options to 'scalar clone' to allow initial clones to take advantage of different cache servers.

The intended use here is to take advantage of new cache server infrastructure as each protocol endpoint is deployed independently.

  • This change only applies to interactions with Azure DevOps and the
    GVFS Protocol.

Note: This PR points at vfs-2.52.0 for review, but I will rebase onto vfs-2.53.0 after that branch is finalized after the Git 2.53.0 release (expected February 2).

In git#836, we implemented custom gvfs.<verb>.cache-server config options
that allow existing enlistments to point specific GVFS Protocol verbs at
different cache servers. However, that did not help at clone time.

This change adds --<verb>-cache-server-url options to 'scalar clone' to
allow initial clones to take advantage of different cache servers.

The intended use here is to take advantage of new cache server
infrastructure as each protocol endpoint is deployed independently.

Signed-off-by: Derrick Stolee <stolee@gmail.com>
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.

1 participant