Spiro Trikaliotis [mailto:[EMAIL PROTECTED] wrote: > not that I would recommend it, but: > > But about > > 1. Taking the CVS repository offline > 2. Create the tarball > 3. Take the CVS repository online with full access (!) > 4. do anything needed to move to the new server > 5. When everything is working fine, take the (original) repository > offline again > 6. Now perform an rsync between the two repositories > 7. Take the new one online (with changing DNS entries and the like). > > Would this make sense, or could 6. break something that was made with > 4.? That would work, as long as nobody checked anything into the new server. We decided to err on the side of safety, rather than take the chance that one of our 150 or so users might discover the new server and check into it when they shouldn't.
-- Jim Hyslop Senior Software Designer Leitch Technology International Inc. (<http://www.leitch.com/>) Columnist, C/C++ Users Journal (<http://www.cuj.com/experts>) _______________________________________________ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
