cvsclient.texi (32896) | cvsclient.texi (34461) |
---|---|
1\input texinfo @c -*- texinfo -*- 2 3@setfilename cvsclient.info 4@include CVSvn.texi 5 6@node Top 7@top CVS Client/Server 8 --- 295 unchanged lines hidden (view full) --- 304@code{Valid-responses} request, containing all the responses it 305supports, followed by a @code{valid-requests} request, which elicits 306from the server a @code{Valid-requests} response containing all the 307requests it understands. In this way, the client and server each find 308out what the other supports before exchanging large amounts of data 309(such as file contents). 310 311@c Hmm, having 3 sections in this menu makes a certain amount of sense | 1\input texinfo @c -*- texinfo -*- 2 3@setfilename cvsclient.info 4@include CVSvn.texi 5 6@node Top 7@top CVS Client/Server 8 --- 295 unchanged lines hidden (view full) --- 304@code{Valid-responses} request, containing all the responses it 305supports, followed by a @code{valid-requests} request, which elicits 306from the server a @code{Valid-requests} response containing all the 307requests it understands. In this way, the client and server each find 308out what the other supports before exchanging large amounts of data 309(such as file contents). 310 311@c Hmm, having 3 sections in this menu makes a certain amount of sense |
312@c but that structure gets lots in the printed manual (not sure about | 312@c but that structure gets lost in the printed manual (not sure about |
313@c HTML). Perhaps there is a better way. 314@menu 315 316General protocol conventions: 317 318* Entries Lines:: Transmitting RCS data 319* File Modes:: Read, write, execute, and possibly more... 320* Filenames:: Conventions regarding filenames --- 1483 unchanged lines hidden --- | 313@c HTML). Perhaps there is a better way. 314@menu 315 316General protocol conventions: 317 318* Entries Lines:: Transmitting RCS data 319* File Modes:: Read, write, execute, and possibly more... 320* Filenames:: Conventions regarding filenames --- 1483 unchanged lines hidden --- |