RE: Re: How to map CVS revision number to migrated SVN revision number
From: Amit Verma <amit.verma_at_rsystems.com>
Date: Fri, 12 Jun 2009 02:28:47 -0700 (PDT)
Hi Ryan
I thank you very much for your reply.
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) -
[[Revision-number: 17]]
[[Node-path: trunk/fmtcrt]]
K 15
As we can see that the sample of dump file contains the current SVN revision number in line [[Revision-number:17]] for the module "fmtcrt" which earlier had revision number [[2.7]] in CVS repository. It also implies that the CVS module "fmtcrt" now has the path [[Node-path: trunk/fmtcrt]].
So it is proved that we can map this (and we have achieved the same for almost 3500+ modules) but the only problem is it becomes recurrsively complicated, specially when it comes to "Node-copyfrom-rev: 523" and "Node-copyfrom-path" in place of "Revision-number:" and "Node-path:" respectively. We need to see a log file for a better understanding.
That is why asked if there some other way to map this? As we require the solution desparately!
Thanks Again.
------------------------------------------------------
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
|
This is an archived mail posted to the Subversion Users mailing list.
This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.