Mac OS X Panther in a Nutshell, 2nd Edition

Name

release

Synopsis

release 
  [ -d ] 
  directory ...

Sandboxes can be abandoned or deleted without using cvs release, but using the release command logs an entry to the history file (if this mechanism is configured) about the sandbox being destroyed. In addition, it checks the disposition (recursively) of each sandbox file before deleting anything. This can prevent destroying work that has not yet been committed.

There is only one option that can be used with the release command: the -d option deletes the sandbox copy if no uncommitted changes are present.

Note

New directories (including any files in them) in the sandbox will be deleted if the -d option is used with release.

The status codes listed in Table 17-25 describe the disposition of each file encountered in the repository and the sandbox.

Table 17-25. release status codes

Status	Description
A	The sandbox file has been added (the file was created, and cvs add was run), but the addition has not been committed.
M	The sandbox copy of the file has been modified.
P U	Update available. There is a newer version of the file in the repository, and the copy in the sandbox has not been modified.
R	The sandbox copy was removed (the file was deleted, and cvs remove was run), but the removal was not committed.
?	The file is present in the sandbox but not in the repository.