User-Agent string, my patch and privacy concerns.

[Martin Geisler]

Matt Mackall <mpm at selenic.com> writes:

> On Wed, 2008-04-02 at 20:24 +0200, Martin Geisler wrote:
>> "Eric M. Hopper" <hopper at omnifarious.org> writes:
>> 
>> > [...] If a maintainer is thinking of moving to a version of
>> > Mercurial that may do things an older version won't understand
>> > fully, it would be nice to know how much of an impact that's
>> > going to have independent of who complains the loudest.
>> 
>> Can't you already tell this from the protocol version which
>> Mercurial already tells you?
>> 
>> I assume the protocol version would be changed if the new Mercurial
>> is not backwards compatible.
>
> The wire protocol has never changed in a way that would warrant
> bumping the version number and is in fact unlikely to. We've added a
> couple things to it, but in a fashion that allows backwards
> compatibility.

I guess that was also my point: if the client/server evolves without
breaking the protocol, then one could easily upgrade the server
without effecting the clients.

-- 
Martin Geisler

VIFF (Virtual Ideal Functionality Framework) brings easy and efficient
SMPC (Secure Multi-Party Computation) to Python. See: http://viff.dk/.