Advanced CVS
I'll just note that it is possible to tell CVS to "watch" a file and notify you (via email for example) when someone changes it.
There are also troubleshooting tips in the red-bean CVS book and the Cederquest CVS manual
The chapter on CVS that comes from the book being published on the Netbeans IDE (listed in the Resource section) talks about renaming your working directory every few days and checking out a complete new copy of the system. This shows anything that is missing while you still have a copy (in the renamed folder) to recover with.
Suggestion: When you make a major release of a large software package, it is worthwhile to create a secondary project and version control everything that it takes to build a working copy of the software. This would include the install package for the compiler, any libraries that are used in compiling the package. Then go to a brand new PC and checkout everything and see if you can build the whole software package. Keep adding things to your repositories until you can rebuild your whole release. This helps to guarantee that 10 years from now when a customer wants to pay you to fix or add something you will be able to find all the little pieces that went into the package. On some projects, I have kept one machine with a Ghost copy of the original install just for this purpose. We would take the PC back to the original install state and then see if we could get to the final product without contortions that no one would remember 10 years later.
Another suggestion is to keep a files as part of your project called notes.java or notes.c or notes.prg. This will get version controlled, zipped up when you zip *.java, etc. This is one place where you can put notes to yourself about special considerations, things to-do, etc. and know that it will travel with the source code of the project.
There is also considerably more on moving folders, renaming files and much, much more.