summaryrefslogtreecommitdiff
path: root/walker.c
diff options
context:
space:
mode:
authorLibravatar Stefan Karpinski <stefan.karpinski@gmail.com>2009-01-29 17:12:27 -0800
committerLibravatar Junio C Hamano <gitster@pobox.com>2009-01-30 21:06:27 -0800
commit499cc56a60b5c90415c74857035579713a07fa1b (patch)
tree133588dc8341e123e6fa24ab4444acd92c6ad200 /walker.c
parentUpdate draft release notes to 1.6.2 (diff)
downloadtgif-499cc56a60b5c90415c74857035579713a07fa1b.tar.xz
git-cvsserver: handle CVS 'noop' command.
The CVS protocol documentation, found at http://www.wandisco.com/techpubs/cvs-protocol.pdf states the following about the 'noop' command: Response expected: yes. This request is a null command in the sense that it doesn't do anything, but merely (as with any other requests expecting a response) sends back any responses pertaining to pending errors, pending Notified responses, etc. In accordance with this, the correct way to handle the 'noop' command, when issued by a client, is to call req_EMPTY. The 'noop' command is called by some CVS clients, notably TortoiseCVS, thus making it desirable for git-cvsserver to respond to the command rather than choking on it as unknown. Signed-off-by: Stefan Karpinski <stefan.karpinski@gmail.com> Signed-off-by: Junio C Hamano <gitster@pobox.com>
Diffstat (limited to 'walker.c')
0 files changed, 0 insertions, 0 deletions