[cvsnt] Moving CVS, does everyone have to commit their work before the move?

Mark Johnson amarkjohnson at gmail.com
Sat Jul 14 20:53:32 BST 2007

Community technical support mailing list was retired 2010 and replaced with a professional technical support team. For assistance please contact: Pre-sales Technical support via email to sales@march-hare.com.

If you happen to have WinCVS on your client machines, then you can run the
change CVSROOT script to change the root on your client machines to point to
the new machine & cvsroot.  This simplifies the "hack".


On 7/13/07, Flávio Etrusco <flavio.etrusco at gmail.com> wrote:
> On 7/13/07, Jerome Fong <jfong at successmetricsinc.com> wrote:
> > Hi there,
> >
> > I'm planning to move CVS from the current machine to a different server.
> > After setting up the CVS server, I was going to copy the entire CVS tree
> > from the old machine to the new machine.  Then, have everyone point to
> > the new machine.
> >
> > Does everyone need to check in their outstanding changes before I make
> > my copy or is it alright to copy with uncommitted changes outstanding?
> >
> It's not strictly necessary, but if the server or repository name are
> going to change then it's very recommended. Otherwise, you'll have to
> "hack" all sandboxes to point to the new CVSROOT URL.
> Other than that, the revision number, tags and everything remains the
> same.
> Best regards,
> Flávio
> _______________________________________________
> cvsnt mailing list
> cvsnt at cvsnt.org cvsnt downloads at march-hare.com @CVSNT on Twitter CVSNT on Facebook
> http://www.cvsnt.org/cgi-bin/mailman/listinfo/cvsnt https://www.march-hare.com/cvspro/en.asp#downcvs

More information about the cvsnt mailing list
Download the latest CVSNT, TortosieCVS, WinCVS etc. for Windows 8 etc.
@CVSNT on Twitter   CVSNT on Facebook