Re: [RFC 0/7] transitioning to protocol v2
- From
Jeff King <peff@peff.net>
- Date
- Aug 25, 2017, 17:36 UTC
- Message-ID
- <20170825173627.gic5gdu7dv7zxucj@sigill.intra.peff.net>
- In-Reply-To
- <xmqqbmn3tvru.fsf@gitster.mtv.corp.google.com>
On Fri, Aug 25, 2017 at 10:14:13AM -0700, Junio C Hamano wrote:
Show 13 quoted lines
> Stefan Beller <sbeller@google.com> writes: > > > For now I would suggest we put a protocol v2 in place that is > > the current protocol + a version number coming through the > > poked hole at the beginning; the goal and review of this series > > ought to focus on getting the version handshake right... > > Oh, we are in absolute agreement on that. It would be nice if we > can have new tests to demonostrate three combinations working well > (i.e. use 'installed git' whose path is given externally on one end > of the connection, while the just-built binary sits on the other > end, in addition to making sure just-built binary successfully talks > with itself).
The harness in t/interop can perhaps help with that (at least between existing git versions; testing across other implementations makes the setup a lot tricker).
-Peff