From: Piotr Szlazak Date: Sat, 19 Oct 2024 16:39:57 +0000 (+0000) Subject: doc: document how uploadpack.allowAnySHA1InWant impact other allow options X-Git-Tag: v2.48.0-rc0~83^2 X-Git-Url: http://git.ipfire.org/?a=commitdiff_plain;h=bddfccead1f4a94f4029d1efeacaed0d23e2fbb4;p=thirdparty%2Fgit.git doc: document how uploadpack.allowAnySHA1InWant impact other allow options Document how setting of `uploadpack.allowAnySHA1InWant` influences other `uploadpack` options - `allowTipSHA1InWant` and `allowReachableSHA1InWant`. Signed-off-by: Piotr Szlazak Signed-off-by: Taylor Blau --- 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