"Shawn O. Pearce" <spearce@xxxxxxxxxxx> writes: > Show Refs > --------- > > Obtains the available refs from the remote repository. The response > is a sequence of git "packet lines", one per ref, and a final flush > packet line to indicate the end of stream. As the initial protocol exchange request, I suspect that you would regret if you do not leave room for some "capability advertisement" in this exchange. With the git native protocol, we luckily found space to do so after the ref payload (because pkt-line is "length + payload" format but the code that reads payload happened to ignore anything after NUL). You would want to define how these are given by the server to the client over HTTP channel. For example, putting them on extra HTTP headers is probably Ok. -- 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
