diff options
| author |  David Turner <dturner@twosigma.com> | 2016-11-11 12:23:48 -0500 |
|---|---|---|
| committer |  Junio C Hamano <gitster@pobox.com> | 2016-11-18 13:06:14 -0800 |
| commit | f8edeaa05d8623a9f6dad408237496c51101aad8 (patch) | |
| tree | faf475f7743ddb59bcde10bb1ba495f426153d45 /Documentation | |
| parent | remote-curl: don't hang when a server dies before any output (diff) | |
| download | tgif-f8edeaa05d8623a9f6dad408237496c51101aad8.tar.xz | |
upload-pack: optionally allow fetching any sha1
It seems a little silly to do a reachabilty check in the case where we
trust the user to access absolutely everything in the repository.
Also, it's racy in a distributed system -- perhaps one server
advertises a ref, but another has since had a force-push to that ref,
and perhaps the two HTTP requests end up directed to these different
servers.
Signed-off-by: David Turner <dturner@twosigma.com>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
Diffstat (limited to 'Documentation')
| -rw-r--r-- | Documentation/config.txt | 5 | ||||
| -rw-r--r-- | Documentation/git-fetch-pack.txt | 6 |
2 files changed, 8 insertions, 3 deletions
diff --git a/Documentation/config.txt b/Documentation/config.txt index a0ab66aae7..b7f9991cc7 100644 --- a/Documentation/config.txt +++ b/Documentation/config.txt @@ -2961,6 +2961,11 @@ uploadpack.allowReachableSHA1InWant:: calculating object reachability is computationally expensive. Defaults to `false`. +uploadpack.allowAnySHA1InWant:: + Allow `upload-pack` to accept a fetch request that asks for any + object at all. + Defaults to `false`. + uploadpack.keepAlive:: When `upload-pack` has started `pack-objects`, there may be a quiet period while `pack-objects` prepares the pack. Normally diff --git a/Documentation/git-fetch-pack.txt b/Documentation/git-fetch-pack.txt index d45f6adc69..f7ebe36a7b 100644 --- a/Documentation/git-fetch-pack.txt +++ b/Documentation/git-fetch-pack.txt @@ -119,9 +119,9 @@ be in a separate packet, and the list must end with a flush packet. $GIT_DIR (e.g. "HEAD", "refs/heads/master"). When unspecified, update from all heads the remote side has. + -If the remote has enabled the options `uploadpack.allowTipSHA1InWant` or -`uploadpack.allowReachableSHA1InWant`, they may alternatively be 40-hex -sha1s present on the remote. +If the remote has enabled the options `uploadpack.allowTipSHA1InWant`, +`uploadpack.allowReachableSHA1InWant`, or `uploadpack.allowAnySHA1InWant`, +they may alternatively be 40-hex sha1s present on the remote. SEE ALSO -------- |