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.
I found it. It was an eclipse problem. Well, rather, it was a problem in that I didn't know how to make eclipse check for versions properly. It's quite different than WinCVS. I had done what you said, so I figured it had to be on the eclipse side. Thanks Joelle Tegwen Bo Berglund wrote: >I assume you have the old repository still available? >If so then look at two RCS files from both and compare them. They >should only differ if there hase been committed edits in the new >server after you moved. > >The RCS files contain in themselves the *full* history of the file >they represent, so unless you did something really screwy when moving >to the new server that information should still be around. > >The proper way to move a repository to a new server is the following >(my view at least): >1. Stop the CVSNT services on the old server >2. Copy the full repository tree from the old to the new server >3. In the CVSNT control panel of the new server add the existing >repositories you just copied and name them exactly like they were >named in the old server. >4. In your DNS change the record that points to the old server to now >point to the new server. (Change the IP address of the old record). >5. Start the CVSNT services on the new server. > >By doing this your users need not even modify their existing checked >out sandboxes as they would have to if the server name has changed. > > >/Bo Berglund >_______________________________________________ >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 > > >