[EMAIL PROTECTED] on 02/13/2000 10:13:16 AM >On Saturday, February 12, Paul Sander wrote: >> There are several forms of migration, of course. One obvious one is >> the conversion from one source control system to another system. Another >> form of migration is replicating a repository for any of a number of >> purposes. In any case, there are multiple repositories undergoing >> modification: At least one of them has new development changes introduced >> to its contents while all of the rest have existing revisions propagated to >> them. > >Certainly. I've migrated CVS to CVS before as well. What you are asking in >general terms here, is the ability to have separate repos, and have CVS do the >managing of propogating diffs to the various repos. I hate to say it, but CVS >does not do that. Have a look at PRCS, as far as I understand it, that is one >of the primary reasons for PRCS client-server to exist. At least there you'd >be starting with a base designed with this in mind. I've proposed in the past that a CVSROOT_RO variable and CVS/Root_ro file be added to point to a copy of the repo solely used for read-only operations. Of course, the locks will still have to be created within the master repo. I think rsync can be used to synch the read-only copies with the master copy. This is a worthwhile task for anyone willing, but unfortunately I currently don't have the time to make this change. Noel
