On Sat, Feb 28, 2015 at 8:01 AM, Stefan Beller <sbeller@xxxxxxxxxx> wrote: > diff --git a/Documentation/technical/protocol-capabilities.txt b/Documentation/technical/protocol-capabilities.txt > index 4f8a7bf..40ddb37 100644 > --- a/Documentation/technical/protocol-capabilities.txt > +++ b/Documentation/technical/protocol-capabilities.txt > @@ -3,6 +3,10 @@ Git Protocol Capabilities > > Servers SHOULD support all capabilities defined in this document. > > +The client MAY ask for capabilities first out of band to the server. > +If so the server MUST NOT advertise any capabilities the client did > +not ask for. I think what the current patches do is "For v2, the client must _tell_ the server its capabilities". The unwritten statement is "the server must not use any capabilities not advertised by the client". v2 will not send initial refs by default, and the client will need to send "wantrefs refs/heads/* refs/tags/*" or similar to retrieve ref list. So we don't have any client capability yet. But there are two caps that come to mind: - ref list compression (for sending full ref list in clone), compression ratio may be 50% - setting locale in upload-pack and receive-pack to support l10n. > On the very first line of the initial server response of either > receive-pack and upload-pack the first reference is followed by > a NUL byte and then a list of space delimited server capabilities. This one should be prefixed with "in version 1, " -- Duy -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html