From: Piotr Szlazak <piotr.szlazak@gmail.com>
To: Piotr Szlazak via GitGitGadget <gitgitgadget@gmail.com>,
git@vger.kernel.org
Cc: Christian Couder <chriscool@tuxfamily.org>,
Taylor Blau <me@ttaylorr.com>, Jeff King <peff@peff.net>
Subject: Re: [PATCH v2] doc: document how uploadpack.allowAnySHA1InWant impact other allow options
Date: Mon, 21 Oct 2024 07:55:06 +0200 [thread overview]
Message-ID: <fd5fab45-1363-41c8-915a-5578a35d219d@gmail.com> (raw)
In-Reply-To: <72184384-07ff-4f74-91d7-280ca78407b5@gmail.com>
On 19.10.2024 18:46, Piotr Szlazak wrote:
>
> On 19.10.2024 18:39, Piotr Szlazak via GitGitGadget wrote:
>> 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
>
> PATCH v2 which updates documentation.
>
> I wrote 'By default not set', as definitely 'Defaults to `false`' in
> not true.
>
> Only when `uploadpack.allowAnySHA1InWant` set to `true` or `false` it
> will affect reported capabilities.
>
> Regards,
>
> Piotr
On the second look code changes will be needed, as at the moment final
result will differ between:
[uploadpack]
allowTipSHA1InWant = true
allowReachableSHA1InWant = true
allowAnySHAInWant = false
and:
[uploadpack]
allowAnySHAInWant = false
allowTipSHA1InWant = true
allowReachableSHA1InWant = true
Regards,
Piotr
next prev parent reply other threads:[~2024-10-21 5:55 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 ` [PATCH v2] doc: document how uploadpack.allowAnySHA1InWant impact other allow options Piotr Szlazak via GitGitGadget
2024-10-19 16:46 ` Piotr Szlazak
2024-10-21 5:55 ` Piotr Szlazak [this message]
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=fd5fab45-1363-41c8-915a-5578a35d219d@gmail.com \
--to=piotr.szlazak@gmail.com \
--cc=chriscool@tuxfamily.org \
--cc=git@vger.kernel.org \
--cc=gitgitgadget@gmail.com \
--cc=me@ttaylorr.com \
--cc=peff@peff.net \
/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).