summaryrefslogtreecommitdiff
path: root/fetch-pack.h
diff options
context:
space:
mode:
authorBrandon Williams <bmwill@google.com>2018-03-15 17:31:42 (GMT)
committerJunio C Hamano <gitster@pobox.com>2018-03-15 19:01:09 (GMT)
commita4d78ce26bf4816d868be21c7355d0e0940460a7 (patch)
treecc2dadefa0e704d7c6650a3294721d586eb715dc /fetch-pack.h
parent0f1dc53f45d307c8342bf547d79695b614cf9c26 (diff)
downloadgit-a4d78ce26bf4816d868be21c7355d0e0940460a7.zip
git-a4d78ce26bf4816d868be21c7355d0e0940460a7.tar.gz
git-a4d78ce26bf4816d868be21c7355d0e0940460a7.tar.bz2
remote-curl: don't request v2 when pushing
In order to be able to ship protocol v2 with only supporting fetch, we need clients to not issue a request to use protocol v2 when pushing (since the client currently doesn't know how to push using protocol v2). This allows a client to have protocol v2 configured in `protocol.version` and take advantage of using v2 for fetch and falling back to using v0 when pushing while v2 for push is being designed. We could run into issues if we didn't fall back to protocol v2 when pushing right now. This is because currently a server will ignore a request to use v2 when contacting the 'receive-pack' endpoint and fall back to using v0, but when push v2 is rolled out to servers, the 'receive-pack' endpoint will start responding using v2. So we don't want to get into a state where a client is requesting to push with v2 before they actually know how to push using v2. Signed-off-by: Brandon Williams <bmwill@google.com> Signed-off-by: Junio C Hamano <gitster@pobox.com>
Diffstat (limited to 'fetch-pack.h')
0 files changed, 0 insertions, 0 deletions