[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: Stephen Butler <sbutler_at_elego.de>
Date: Fri, 12 Jun 2009 11:17:20 +0200

Quoting Ryan Schmidt <subversion-2009b_at_ryandesign.com>:

> 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.

The cv2svn program goes to great lengths to make the newly-created
Subversion history realistic, but a perfect translation is seldom
possible when migrating from any file-oriented VC tool to a tree-
oriented tool like Subversion.

It's a bit late in the game, but did you take advantage of the following
cvs2svn option?

     --cvs-revnums record CVS revision numbers as file properties

Also, cvs2svn will by default copy files that are CVS-tagged into the
corresponding Subversion directories under ^/tags. That would give your
team some orientation points.

Going forward, you need to redesign your development process to use
Subversion repository revision numbers instead of CVS file versions.


Stephen Butler | Software Developer
elego Software Solutions GmbH
Gustav-Meyer-Allee 25 | 13355 Berlin | Germany
fon: +49 30 2345 8696 | mobile: +49 163 25 45 015
fax: +49 30 2345 8695 | http://www.elegosoft.com
Geschäftsführer: Olaf Wagner | Sitz der Gesellschaft: Berlin
Amtsgericht Charlottenburg HRB 77719 | USt-IdNr: DE163214194
Received on 2009-06-12 11:18:17 CEST

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