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 use WinCvs then there is a macro that can be used to modify the sandbox metadata to point to the new server. This is called CHANGEROOT. If you don't have such a front end to CVS then you can manually go in and edit the CVS/Root files that exist in all sandbox directories and change ServerA to ServerB. After this you will be able to commit your modifications just fine. /Bo -----Original Message----- From: cvsnt-bounces at cvsnt.org [mailto:cvsnt-bounces at cvsnt.org]On Behalf Of dario Sent: den 9 november 2004 14:35 To: cvsnt at cvsnt.org cvsnt downloads at march-hare.com @CVSNT on Twitter CVSNT on Facebook Subject: [cvsnt] moving modules to another server? there is working copy pulled from serverA which is dead now. module directory is manualy copied from repository at srvA to repository at srvB. now i am able to get working copy from srvB. that seems to be OK! BUT, that first working copy from srvA was not commited to srvA and i need these changes commited to srvB. is that possible? as i noticed in CVS directory there is "root" file which says where is the server. maybe changing that (i wouldn't like doing it)? my client is TortoiseCVS and srvB is cvsnt 2.0.58. i guess that copying manualy repositories didn't do any harm. thanks for nay suggestions! dario _______________________________________________ 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