From: Junio C Hamano <gitster@pobox.com>
Date: Mon, 16 May 2011 22:12:17 GMT
Subject: Re: [PATCHv3 6/9] receive-pack: Prepare for addition of the new 'limit-*' family of capabilities
Message-ID: <7vd3jijnwe.fsf@alter.siamese.dyndns.org>
In-Reply-To: <BANLkTimge=rPe6K3rYRqYDGQTN_wbi3a2A@mail.gmail.com>

Sverre Rabbelier <srabbelier@gmail.com> writes:

> On Mon, May 16, 2011 at 15:07, Junio C Hamano <gitster@pobox.com> wrote:
>> The old clients treat it as SP separted list, e.g. "featurea featureb featureb",
>> from the beginning of how capabilities[] code was writte, so I do not see
>> a point. I would expect an arbitrary string values would be encased in
>> something like base64, base85 or hex.
>
> Right, that's my point, do we want to leave it up to each individual
> option to decide what encoding to use?

I do not see any point in deciding that right now without even knowing
what kind of strings (short? mostly ascii? etc.) we would typically want
as payload and tie our hands with a poor decision we would end up making
out of thin air.

That is what I meant by "I do not see a point".