diff options
Diffstat (limited to 'Documentation')
| -rw-r--r-- | Documentation/technical/protocol-capabilities.txt | 23 |
1 files changed, 23 insertions, 0 deletions
diff --git a/Documentation/technical/protocol-capabilities.txt b/Documentation/technical/protocol-capabilities.txt index eaab6b4ac7..8c4a0b90ca 100644 --- a/Documentation/technical/protocol-capabilities.txt +++ b/Documentation/technical/protocol-capabilities.txt @@ -275,3 +275,26 @@ to accept a signed push certificate, and asks the <nonce> to be included in the push certificate. A send-pack client MUST NOT send a push-cert packet unless the receive-pack server advertises this capability. + +interesting-refs +---------------- + +For HTTP(S) servers only: + +Whether or not the upload-pack server advertises this capability, +fetch-pack may send a "refspec" parameter in the query string of a +fetch request. This capability indicates that such a parameter will +be respected, in case the client cares. + +Whenever the receive-pack server gets that parameter, it will not +advertise all refs and will instead only advertise refs that match +those listed in the header. The parameter is a space-separated list of +refs. A ref may optionally contain up to one wildcard. +Advertisements will still respect hideRefs. + +The presence or absence of the "refspec" parameter does not affect +what refs a client is permitted to fetch; this is still controlled in +the normal fashion. + +This saves time in the presence of a large number of refs, because the +client need not wait for the server to send the complete list of refs. |