Name
release
Synopsis
release
[ -d ]
directory Sandboxes can be abandoned or deleted without using cvs release if desired; 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 of the sandbox files before deleting anything. This can help prevent destroying work that has not yet been committed.
There is only one option that can be used with the
release command, -d. The
-d option deletes the sandbox copy if no
uncommitted changes are present.
Tip
New directories (including any files in them) in the sandbox are deleted if the -d option is used with release.
The status codes listed in Table 18-34 are used to describe the disposition of each file encountered in the repository and the sandbox.
Table 18-34. release status codes
|
Status |
Description |
|---|---|
|
|
The sandbox file has been added (the file was created and cvs add was run), but the addition has not been committed. |
|
|
The sandbox copy of the file has been modified. |
|
|
Update available. There is a newer version of the file in the repository, and the copy in the sandbox has not been modified. |
|
|
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. |