in reply to
Re: Using CVS for revision control
in thread Using CVS for revision control
There is one action that's lacking in the CVS command set. You cannot rename a file other than manually modifying the repository and the admin files. This is troublesome if many developers have checked out the module.
You're right, there is no way of renaming a file while keeping track of this change in cvs, but
instead of manually messing around with the administration files, you (AFAIK) would (in your working dir):
- $> mv myfile ~/backups
- $> cvs remove myfile
- $> cvs commit myfile
- $> mv ~/backups/myfile newname
- $> cvs add newname
- $> cvs commit newname
This is one of the few ugly parts of CVS; but while your starting to use it, you may give meta-cvs a try. I did not, because of my high workload there's no time for such improvements :-(, but it seems to be worth a try.