The file will then be scheduled for removal from the repository the next time you do a commit. Once committed, the file will be officially deleted from the current version of the repository. However, cvs won't throw this file away, and will still keep a complete record of its contents and its history, just in case you need it back in the future. This is just one of the many ways that cvs protects your valuable source code.

"cvs remove" is recursive, which means that you can delete a bunch of files, and then run the "cvs remove" command with no other arguments from a parent directory. Doing this will cause all of the deleted files to be tagged for removal at the next commit.