Hi, CVSup doesn't depend on CVS (it can work with non CVS files). But for CVS (more precisly RCS) files is more efficient. Thus, it's only up to you which part of cvs repository you will synchronize. Let's suppose your $CVSROOT contains: CVSROOT - cvs admin files global - files to share local - files for local purpose only
If you synchronize only global dir, you can only see changes. Adding CVSROOT you can do check-out but not check-in (you can do checkin via pserver to the original rep.) For details see: www.polstra.com/projects/freeware/CVSup/faq.html >As far as I understand CVSUP lets me get a copy of the whole source tree >from a remote server. This will give me one version of every element >(file). >.... correct? > >What I want is to be able to synchronize the complete repository between >sites. So every site would have the complete history for every file >available (for checkout of a different version *without* having to >contact >the server.) > >(I know that there are issues with concurrency and simultaneous changes. >I can control these ... by doing it the way Ratinal's Clearcase Multisite >does >it.) But is there a technical way to synchronize only the pieces that I >need >to ... ? -- Best regards, Dusan Juhas _______________________________________________ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
