From: Junio C Hamano <gitster@pobox.com>
Date: Thu, 27 Sep 2018 22:20:27 GMT
Subject: Re: [PATCH v2 0/4] Add proto v2 archive command with HTTP support
Message-ID: <xmqq1s9efuqc.fsf@gitster-ct.c.googlers.com>
In-Reply-To: <20180927183017.GD112066@aiede.svl.corp.google.com>

Jonathan Nieder <jrnieder@gmail.com> writes:

>  1. Clients sending version=2 when they do not, in fact, speak protocol
>     v2 for a service is a (serious) bug.  (Separately from this
>     series) we should fix it.
>
>  2. That bug is already in the wild, alas.  Fortunately the semantics of
>     GIT_PROTOCOL as a list of key/value pairs is well defined.  So we
>     have choices of (a) bump version to version=3 (b) pass another
>     value 'version=2:yesreallyversion=2' (c) etc.
>
>  3. This is likely to affect push, too.

Do you mean that existing "git push", "git fetch" and "git archive"
sends version=2 even when they are not capable of speaking protocol
v2?  I thought that "git archive [--remote]" was left outside of the
protocol update (that was the reason why the earlier attempt took a
hacky route of "shallow clone followed by local archive"), so there
is no "git archive" in the wild that can even say "version=$n"
(which requires you to be at least version=1)?