I'm not an expert on such matters, but I believe SVN can assist here if the code is tagged at the time of a new release. This should permit later retrieval of all of the modules corresponding to a particular tag, say "Rev 18".
I'm not too familiar with SVN (yet) - we were using CVS at work and recently migrated to Perforce but based on SVN's CVS heritage I'd expect it to be similar. I'll check with our cvs guru on Monday and see if tagging will help in this respect. I found this SVN link which looks interesting: http://svnbook.red-bean.com/en/1.1/svn-book.pdf Under chapter 4 there is a section on tags. Pete, N3EVL > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of Jim Lux > Sent: Friday, March 17, 2006 8:28 PM > To: [EMAIL PROTECTED]; FlexRadio@flex-radio.biz > Subject: Re: [Flexradio] PowerSDR v1.4.5 Preview 18 is Released > > At 03:19 PM 3/17/2006, Eric Wachsmann - FlexRadio wrote: > >Several things need to be said about this release. > > How do we relate a particular Preview release to a particular > SVN snapshot? > > (i.e., if I wanted to grab a source snapshot for this > release, how would one do it?) > > Jim > > > > _______________________________________________ > FlexRadio mailing list > FlexRadio@flex-radio.biz > http://mail.flex-radio.biz/mailman/listinfo/flexradio_flex-radio.biz > Archive Link: > http://mail.flex-radio.biz/pipermail/flexradio_flex-radio.biz/ > FlexRadio Homepage: http://www.flex-radio.com >