[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: How to map CVS revision number to migrated SVN revision number

From: Ryan Schmidt <subversion-2009b_at_ryandesign.com>
Date: Fri, 12 Jun 2009 03:37:06 -0500

On Jun 12, 2009, at 01:54, Amit Verma wrote:

> We have migrated a huge CVS repository to SVN using CVS2SVN tool
> two weeks back.
> Earlier while our development team was with CVS, we were relying
> heavily on CVS revision numbers for our development process. The
> snapshot of our earlier CVS usages is as -
> cvs co -r "2.1" fmtcrt
> But now because we are with SVN, we need to map those earlier CVS
> revision numbers and module-names (for example "fmtcrt", see above)
> with migrated SVN revision numbers and SVN module path, so that our
> existing development could stay flawless. Here is the snapshot of
> our tried efforts -
> svn co -r "350" file:///home/svn/svnRepository/trunk/fmtcrt
> Here we can see that CVS revision number "2.1" has been mapped to
> SVN revision number "350" and the CVS module "fmtcrt" has been
> mapped to SVN path "trunk/fmtcrt", within the SVN present
> repository "home/svn/svnRepository/".
> Now, because our CVS repository had huge volume of modules
> (multiply this with several CVS revision number for each and every
> CVS module), it is becoming very hard for us to map these revision
> number and module-name from CVS to SVN for our entire team for last
> two weeks.
> Is there a way we can map CVS revision number to migrated SVN
> revision number? Please help and thank you very much in advance.

In CVS, files have revision numbers. In Subversion, the repository as
a whole has revision numbers. So I don't know that you will be able
to create a mapping between these two different concepts.


To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2009-06-12 10:38:10 CEST

This is an archived mail posted to the Subversion Users mailing list.