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/config.txt | |
| parent | 296b847c0d6de63353e236cfbf94163d24155529 (diff) | |
| download | git-f8edeaa05d8623a9f6dad408237496c51101aad8.tar.gz | |
upload-pack: optionally allow fetching any sha1dt/smart-http-detect-server-going-away
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/config.txt')
| -rw-r--r-- | Documentation/config.txt | 5 |
1 files changed, 5 insertions, 0 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 |