[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: Michael Haggerty <mhagger_at_alum.mit.edu>
Date: Tue, 16 Jun 2009 16:10:29 +0200

Amit Verma wrote:
> Whatever you mentioned is true though this is also true that mapping
> between the two repositories is very much possible. I achieved to some
> extent on my own, though it is quite complicated.
> As I mentioned earlier, I used following command to take the dump of
> the SVN repository -
> svnadmin dump home/svn/svnRepository > svnDump
> This dump file has the sequential listing of “cvs2svn:cvs-rev”
> parameters for all the migrated CVS modules. For example (relevant lines
> have been put in [[]] brackets) -
> [...]
> That is why asked if there some other way to map this? As we require
> the solution desparately!

It is certainly not necessary to dump your SVN repository to get access
to these cvs2svn:cvs-rev properties. To see the value of the property
for a specific version of a file, simply type

    svn propget -r 17 cvs2svn:cvs-rev $URL/trunk/fmtcrt

Admittedly, this is the inverse of the mapping that you want, but the
best approach is probably to compute the mapping once and record it in a
file that can be referenced when needed.

It is a pity that you didn't realize this problem *before* switching
over to SVN, because there would have been several things that you could
have done to retain this information during the conversion rather than
having to fish it out afterwards. Indeed, if you ran the conversion in
verbose mode and saved its output, I think the file CVS revision numbers
are listed as each SVN revision is created.



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

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