Heya,
On Mon, May 16, 2011 at 15:07, Junio C Hamano [off-list ref] 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?
--
Cheers,
Sverre Rabbelier