Re: [PATCH] config: option transfer.ipversion to set transport protocol version for network fetches
- From
Alex Riesen <alexander.riesen@cetitec.com>
- Date
- Sep 17, 2020, 08:18 UTC
- Message-ID
- <20200917081854.GC8079@pflmari>
- In-Reply-To
- <xmqqtuvxwkbz.fsf@gitster.c.googlers.com>
Junio C Hamano, Wed, Sep 16, 2020 22:14:08 +0200:
Show 11 quoted lines
> Alex Riesen <alexander.riesen@cetitec.com> writes: > > > Affecting the transfers caused by git-fetch, the > > option allows to control network operations similar > > to --ipv4 and --ipv6 options. > > ... > > Something like this? > > Also, we should follow the usual "the last one wins" for a > configuration variable like this, which is *not* a multi-valued > variable. ...
...
Show 5 quoted lines
> [Footnote] > > *1* But leave a room to extend it in the future to a comma-separated > list of them to allow something like "ipv6,ipv7,ipv8" (i.e. "not > just 'any'---we want to say that 'ipv4' is not welcomed").
I think this footnote is the best description of this option. From what I gathered, it looks like really a list of protocols the networking code is allowed to try to reach the remote.
The above is orthogonal to how it given on the command-line: there it can be "unset". It is just not "unset" for the networking code, rather reset to the default list of protocols.