summaryrefslogtreecommitdiffstats
path: root/usr.bin/cvs/resp.c (follow)
Commit message (Collapse)AuthorAgeFilesLines
* since we close the handles to Entries files, we must reopen them to addjfb2005-01-271-3/+5
| | | | | | the directories when receiving a Clear-sticky or Set-sticky response. spotted by Joris Vink
* when warning about unimplemented handlers, do not attempt to printjfb2005-01-131-2/+2
| | | | the errno message string
* check the return value of a strdup() call and return an error onjfb2005-01-061-1/+6
| | | | | | failure from Joris Vink
* yet another mistake in the protocol docs...even if we send thejfb2004-12-131-2/+2
| | | | | | appropriate Entry for a file which was lost locally, the server responds with a Created, so we must remove the previous entry before replacing it with the one we receive.
* free the buffer used to receive a file in the Updated response handlerjfb2004-12-131-10/+14
| | | | | | and saner handling of checksums spotted by and discussed with Joris Vink
* fix the Copy-file response handler, it seems the CVS protocoljfb2004-12-101-5/+15
| | | | documentation is not exactly up to date for that handler as well
* simplify the handler for Created, Updated, Update-existing and Mergedjfb2004-12-081-16/+22
| | | | | | and close the Entries file handle when we are done modifying it. this fixes a leak and syncs the contents on disk so the revisions and dates get updated properly
* support for the `Copy-file' responsejfb2004-12-081-2/+29
|
* less whitespace, more pretty. ok jfbtedu2004-12-071-22/+6
|
* avoid a crash when receiving either a Created, Updated, Update-existingjfb2004-12-071-11/+26
| | | | | | | or Merged response by reopening the Entries file correctly before making modifications to it Fixes a SIGSEGV reported by Joris Vink and djm@
* tighten vertical spacing for else; jfb okderaadt2004-12-061-17/+9
|
* implement a saner handler for the Removed and Remove-entry responses.jfb2004-12-061-7/+17
| | | | in the case of Removed, the file will actually be unlinked now.
* When receiving a `Checked-in' response, update the Entries informationjfb2004-12-031-2/+24
| | | | | | | | | correctly. This fixes the problem caused by a commit not updating the information properly and subsequent commands generating a message similar to: Merging differences between 1.X and 1.Y into file file already contains the differences between 1.X and 1.Y
* Rewrite the internals of the file management code so that we do not keepjfb2004-11-261-3/+4
| | | | | | a full path to each file we load, and cache file names so we can have multiple references to a single name. This saves a lot of memory on large trees such as /usr/src, especially on 'Makefile', 'README' and such.
* print error messages when we receive the `error' responsejfb2004-09-231-1/+2
|
* Remove unused variablesjfb2004-08-131-3/+1
|
* * add an entry for directories when we create themjfb2004-08-131-3/+15
| | | | * when writing a directory entry, skip the revision and timestamp
* Assume the parent's Entries file is always opened when receiving a newjfb2004-08-131-107/+63
| | | | | entry to add, and move to using the `ce_mtime' field of the entry so we don't end up adding data from a local variable that was discarded
* Cleanup and fix a call to cvs_splitpath()jfb2004-08-061-7/+8
|
* When creating a file, set its last access and modification times to thejfb2004-08-031-2/+10
| | | | last timestamp received by the `Mod-time' command
* Move all of the request- and response-specific handlers into separatejfb2004-08-031-0/+735
files and have only the generic function of each type available to the outside
Copyright © 1996 – 2023 Jason A. Donenfeld. All Rights Reverse Engineered.