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.
> When I started using CVS we had lots of projects where we had archived > snapshots (usually from some release point) using WinZip. > What I did back then was to first expand the very first such snapshot > and then CVS import it. > > Then I checked out the imported source tree into a sandbox structure > (not needed anymore since CVSNT can create the sandbox upon import). > > Next I tagged the sandbox with Release_1-0 or some such tag. > > Then I erased all the source files in the sandbox(es) (note: NOT the > CVS subdirs!) and expanded the next zipfile on top. > > Now I could see all the missing files using wincvs so I cvs erased > them. I also could see new files so I cvs added these. Then I > committed the project from the top and tagged it Release_1-1. > > Repeated the above for all saved snapshots until we were in sync. > This was a straightforward job, but rather dull. > > I believe that the same procedure could be automated, you only need to > have some programmatic way to check out from your current system and > then put it into the new cvsnt system. > I would not care about intermediate revisions of files, just go for > the releases in this initial stage. Unless you desperately need > everything, in which case you have to also get at the log messages > from the old system so it can be used with the new one. > > HTH > > /Bo > (Bo Berglund, developer in Sweden) Hi Bo Never mind, I've found the way how to do that through code Luck was dlls and unit with exported funcions, all revisios can be "catched" Srdjan