What I would have done is set up a cname record in my DNS configuration to give a symbolic name (e.g. "cvsroot") to the machine, in addition to its regular host name. That way if the server moves around, then a quick tweak to the DNS server will give all of the users access again with no changes to their environments.
If you choose to go this route, then the old host's name becomes the symbolic name of the CVS server. --- Forwarded mail from [EMAIL PROTECTED] We are moving our CVS repository to a different machine soon. We currently use the actual machine name that holds our repository in the CVSROOT so any projects that are checked-out have this machine name in the CVS\root file. We have more than 100 projects using CVS. Do we have to have everyone commit all changes before we move the repository to the new machine and have them do a fresh checkout or can we just write a script to update all for the CVS\root files to use the new alias? Or better yet, is there something in CVS or WinCVS to do this? --- End of forwarded message from [EMAIL PROTECTED] _______________________________________________ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
