From: "Piotr Szlazak via GitGitGadget" <gitgitgadget@gmail.com>
To: git@vger.kernel.org
Cc: Christian Couder <chriscool@tuxfamily.org>,
Taylor Blau <me@ttaylorr.com>, Jeff King <peff@peff.net>,
Piotr Szlazak <piotr.szlazak@gmail.com>,
Piotr Szlazak <piotr.szlazak@gmail.com>,
Piotr Szlazak <piotr.szlazak@gmail.com>
Subject: [PATCH v2] doc: document how uploadpack.allowAnySHA1InWant impact other allow options
Date: Sat, 19 Oct 2024 16:39:57 +0000 [thread overview]
Message-ID: <pull.1814.v2.git.git.1729355997353.gitgitgadget@gmail.com> (raw)
In-Reply-To: <pull.1814.git.git.1729112794671.gitgitgadget@gmail.com>
From: Piotr Szlazak <piotr.szlazak@gmail.com>
Document how setting of `uploadpack.allowAnySHA1InWant`
influences other `uploadpack` options - `allowTipSHA1InWant`
and `allowReachableSHA1InWant`.
Signed-off-by: Piotr Szlazak <piotr.szlazak@gmail.com>
---
doc: document how uploadpack.allowAnySHA1InWant impact other allow
options
Published-As: https://github.com/gitgitgadget/git/releases/tag/pr-git-1814%2Fpszlazak%2Fupload-pack-allow-flags-v2
Fetch-It-Via: git fetch https://github.com/gitgitgadget/git pr-git-1814/pszlazak/upload-pack-allow-flags-v2
Pull-Request: https://github.com/git/git/pull/1814
Range-diff vs v1:
1: 8a2673bdf31 < -: ----------- upload-pack: fix how ALLOW_ANY_SHA1 flag is disabled
-: ----------- > 1: 2a9fa4dabba doc: document how uploadpack.allowAnySHA1InWant impact other allow options
Documentation/config/uploadpack.txt | 6 +++++-
1 file changed, 5 insertions(+), 1 deletion(-)
diff --git a/Documentation/config/uploadpack.txt b/Documentation/config/uploadpack.txt
index 16264d82a72..0e1dda944a5 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
base-commit: 34b6ce9b30747131b6e781ff718a45328aa887d0
--
gitgitgadget
next prev parent reply other threads:[~2024-10-19 16:40 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-16 21:06 [PATCH] upload-pack: fix how ALLOW_ANY_SHA1 flag is disabled Piotr Szlazak via GitGitGadget
2024-10-16 21:18 ` Taylor Blau
2024-10-17 2:37 ` Jeff King
2024-10-17 15:23 ` Taylor Blau
2024-10-17 15:59 ` Piotr Szlazak
2024-10-17 18:46 ` Taylor Blau
2024-10-18 4:33 ` Jeff King
2024-10-18 21:46 ` Taylor Blau
2024-10-19 16:39 ` Piotr Szlazak via GitGitGadget [this message]
2024-10-19 16:46 ` [PATCH v2] doc: document how uploadpack.allowAnySHA1InWant impact other allow options Piotr Szlazak
2024-10-21 5:55 ` Piotr Szlazak
2024-10-21 19:03 ` Jeff King
2024-10-21 19:47 ` Taylor Blau
2024-10-21 19:48 ` Taylor Blau
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=pull.1814.v2.git.git.1729355997353.gitgitgadget@gmail.com \
--to=gitgitgadget@gmail.com \
--cc=chriscool@tuxfamily.org \
--cc=git@vger.kernel.org \
--cc=me@ttaylorr.com \
--cc=peff@peff.net \
--cc=piotr.szlazak@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).