From: Duy Nguyen <pclouds@gmail.com>
Date: Tue, 24 Feb 2015 04:02:05 GMT
Subject: Re: [RFC/PATCH 0/3] protocol v2
Message-ID: <CACsJy8BSf2h_xD-Q1tudAg_xCzffRQM+7xzUgprONxD7vM5RYw@mail.gmail.com>
In-Reply-To: <1424747562-5446-1-git-send-email-sbeller@google.com>

On Tue, Feb 24, 2015 at 10:12 AM, Stefan Beller <sbeller@google.com> wrote:
> One of the biggest problems of a new protocol would be deployment
> as the users probably would not care too deeply. It should just
> work in the sense that the user should not even sense that the
> protocol changed.

Agreed.

> To do so we need to make sure the protocol
> is backwards compatible and works if an old client talks to
> a new server as well as the other way round.

It's very hard to keep backward compatibility if you want to stop the
initial ref adverstisement, costly when there are lots of refs. But we
can let both protocols run in parallel, with the old one advertise the
presence of the new one. Then the client could switch to new protocol
gradually. This way new protocol could forget about backward
compatibility. See

http://thread.gmane.org/gmane.comp.version-control.git/215054/focus=244325
-- 
Duy