diff options
| author |  Jeff King <peff@peff.net> | 2012-08-10 03:57:43 -0400 |
|---|---|---|
| committer |  Junio C Hamano <gitster@pobox.com> | 2012-08-10 12:35:13 -0700 |
| commit | d50c3871632451b0cac066eea178198ac8a9dff1 (patch) | |
| tree | fd9ff70aeef269e251c193ca899cf6bb11f33352 /Documentation/RelNotes/1.7.6.5.txt | |
| parent | send-pack: fix capability-sending logic (diff) | |
| download | tgif-d50c3871632451b0cac066eea178198ac8a9dff1.tar.xz | |
do not send client agent unless server does first
Commit ff5effdf taught both clients and servers of the git protocol
to send an "agent" capability that just advertises their version for
statistics and debugging purposes. The protocol-capabilities.txt
document however indicates that the client's advertisement is
actually a response, and should never include capabilities not
mentioned in the server's advertisement.
Adding the unconditional advertisement in the server programs was
OK, then, but the clients broke the protocol. The server
implementation of git-core itself does not care, but at least one
does: the Google Code git server (or any server using Dulwich), will
hang up with an internal error upon seeing an unknown capability.
Instead, each client must record whether we saw an agent string from
the server, and respond with its agent only if the server mentioned
it first.
Signed-off-by: Jeff King <peff@peff.net>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
Diffstat (limited to 'Documentation/RelNotes/1.7.6.5.txt')
0 files changed, 0 insertions, 0 deletions