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 email@example.com.
> -----Original Message----- > From: cvsnt-bounces at cvsnt.org [mailto:cvsnt-bounces at cvsnt.org]On Behalf > Of Bo Berglund > Sent: Friday, January 16, 2004 12:02 PM > To: cvsnt at cvsnt.org cvsnt downloads at march-hare.com @CVSNT on Twitter CVSNT on Facebook > Subject: [cvsnt] Re: cvsnt does not encrypt > > If you issue any cvs command within a sandbox then it will use the > exact same protocol and server/repository settings as was used when > the files were checked out. > The only ways out are: > 1. Edit all of the Root files in the hidden folders named CVS that > exist in all sandbox folders and change to the protocol you want to > use. This can be done with a macro (Change CVSROOT) if you use WinCvs. > > 2. Check out a fresh copy of the files in some other folder and make > sure to use the correct protocol while checking out. In this case > delete the original sandbox folder where you used the simpler > protocol. > 3. Use the global -d flag, that is what it is for: $ cvs -d %NEW_CVSROOT% update See cvs --help-options. Also if you want to do #1, use one of the change root macros. WinCVS (1.3.5 and greater) comes with a good one written in Python. == Ezra Epstein