...Wow! Let me make sure I have this straight: do you mean that instead of doing
...(and losing all history info in the process, I suppose) I could simply do this
% cp -pr original_repo/myproj new_repo
Yup! You're a quick study. You get an A. :-)
% rm -rf cvs_repository/project_to_remove
? Would this mess up the rest of cvs_repository in any way?
I assume that's $CVSROOT/project_to_remove.
It depends. You might have a problem if project_to_remove is part of a module definition in $CVSROOT/CVSROOT/modules. The modules file is, I believe, the only place where CVS creates dependencies on top-level directories in $CVSROOT. Mentioning a non-existent module in the *info files in $CVSROOT/CVSROOT is benign.
Of course, deleting a module from the repository means that it's no longer there (Duh!). Don't expect CVS operations in a checked out project_to_remove sandbox to work. But, you knew that, didn't you?
Fred
_______________________________________________________________ Frederic W. Brehm, Sarnoff Corporation, http://www.sarnoff.com/
_______________________________________________ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
