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

How to map CVS revision number to migrated SVN revision number

From: Amit Verma <amit.verma_at_rsystems.com>
Date: Thu, 11 Jun 2009 23:54:50 -0700 (PDT)


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.

Note - We used SVN dump to map the CVS revision numbers and module-names to SVN revision numbers and new module-paths altogether. Following is the command we used, to generate the SVN dump file -

svnadmin dump svnRep > svnDumpFile

Amit Verma


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

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