summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorTaylor Blau <me@ttaylorr.com>2024-11-01 12:53:22 -0400
committerTaylor Blau <me@ttaylorr.com>2024-11-01 12:53:22 -0400
commitaabbcf278388dac4198fda4271bf0f6920ab45ed (patch)
tree281bd318c2d04660544d859ba1aff7357e32eb35
parent07c6066f82ff23efccf2a099e3ef5662d8f62c5d (diff)
parentbddfccead1f4a94f4029d1efeacaed0d23e2fbb4 (diff)
Merge branch 'ps/upload-pack-doc'
Documentation update to clarify that 'uploadpack.allowAnySHA1InWant' implies both 'allowTipSHA1InWant' and 'allowReachableSHA1InWant'. * ps/upload-pack-doc: doc: document how uploadpack.allowAnySHA1InWant impact other allow options
-rw-r--r--Documentation/config/uploadpack.txt6
1 files changed, 5 insertions, 1 deletions
diff --git a/Documentation/config/uploadpack.txt b/Documentation/config/uploadpack.txt
index 16264d82a7..0e1dda944a 100644
--- a/Documentation/config/uploadpack.txt
+++ b/Documentation/config/uploadpack.txt
@@ -25,7 +25,11 @@ uploadpack.allowReachableSHA1InWant::
uploadpack.allowAnySHA1InWant::
Allow `upload-pack` to accept a fetch request that asks for any
object at all.
- Defaults to `false`.
+ It implies `uploadpack.allowTipSHA1InWant` and
+ `uploadpack.allowReachableSHA1InWant`. If set to `true` it will
+ enable both of them, it set to `false` it will disable both of
+ them.
+ By default not set.
uploadpack.keepAlive::
When `upload-pack` has started `pack-objects`, there may be a