|
Modelling clouds and climate |
Getting Rid Of A Working Copy |
| Path: Contents > Using CVS > Getting Rid Of A Working Copy | |
|
Site Map
Contents About CVS Terminology Using CVS (import) (checkout) (update/diff) (commit) (release) Other CVS Commands (log) (add/del) Spetial Topics References Web Contact: Phil Austin Site created with Cheetah. Last updated: Mar 13 2003 |
Getting Rid Of A Working Copycvs release (synonyms: re, rel) This option is used when the user doesn't want to use the code any more. In a typical CVS usage, the way to get rid of a working copy directory tree is to remove it like any other directory tree: $ rm -rf myproj (bad) However, if you eliminate your working copy this way, other developers will not know that you have stopped using it. CVS provides a command to relinquish a working copy explicitly. Think of release as the opposite of checkout - you're telling the repository that you're done with the working copy now. Like checkout, release is invoked from the parent directory of the tree: $ pwd ~/projects/ubcscm $ cd .. $ ls ubcscm $ cvs release ubcscm You have [0] altered files in this repository. Are you sure you want to release directory 'ubcscm': y $ If there are uncommitted changes in the repository, release will only lists the modified files. Otherwise, assuming the tree is clean (totally up to date), release records in the repository that the working copy has been released. You can also have release automatically delete the working tree for you, by passing the -d flag: $ ls ubcscm $ cvs release -d ubcscm You have [0] altered files in this repository. Are you sure you want to release (and delete) directory 'ubcscm': y $ ls $ |