[cvsnt] Help importing several vendor releases

Starrett, Glen (AZ15) glen.starrett at honeywell.com
Mon Jul 21 17:42:51 BST 2003


> 1) I put the release 1 in a directory
> 2) I launch : cvs import -m 'importing from xxx' MY_TAG release1
> 3) I empty my directory
> 4) I put the release 2 in the directory

There's an option to test, not actually write anything--I would think that
after your step 4 when you run cvs import .... release2 then you could do a
cvs -n update then cvs rm any 'U' files you get.

Glen Starrett

> -----Original Message-----
> From: bds [mailto:bullesdesavon at yahoo.com]
> Sent: Monday, July 21, 2003 8:18 AM
> To: cvsnt at cvsnt.org
> Subject: [cvsnt] Help importing several vendor releases
> 
> 
> Hi,
> 
> I'm trying to import an history of several release of a product before
> I go on developping new features for it (i.e. I'm changing my version
> control software and I don't want to lose my history).
> 
> Here is what I do:
> 
> 1) I put the release 1 in a directory
> 2) I launch : cvs import -m 'importing from xxx' MY_TAG release1
> 3) I empty my directory
> 4) I put the release 2 in the directory
> ...
> 
> So when I do a checkout on any tag 'releaseX', I get the proper
> revision for every file in the project. Fine.
> 
> My problem is that when I do a checkout without any tag, I get the
> last revsion for every file of the project, *including the files that
> are no longer part of my project*.
> 
> Do you know what I should do to *automatically* remove those files?
> 
> 
> Ex:
> 
> Release 1 contains files A and B
> Release 2 contains files A (modified) and C
> 
> "cvs checkout" gives me A (last revision), B and C; but B should not
> be there anymore.
> 
> Thanks for help,
> 
> BdS
> _______________________________________________
> cvsnt mailing list
> cvsnt at cvsnt.org
> http://www.cvsnt.org/cgi-bin/mailman/listinfo/cvsnt
> 


More information about the cvsnt mailing list