[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: Blair Zajac <blair_at_orcaware.com>
Date: Fri, 12 Jun 2009 11:56:01 -0700

Amit Verma wrote:
> 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]]
> Prop-content-length: 125
> Content-length: 125
> K 7
> svn:log
> V 26
> *** empty log message ***
> K 10
> svn:author
> V 4
> gabe
> K 8
> svn:date
> V 27
> 2002-09-11T20:30:23.000000Z
> PROPS-END
>
> [[Node-path: trunk/fmt​crt]]
> Node-kind: dir
> Node-action: change
> Prop-content-length: 116
> Text-content-length: 5154
> Text-content-md5: 554dd3c63a9a18fbc40af7cc24e2f6b4
> Content-length: 5270
>
> K 15
> [[cvs2svn:cvs-rev]]
> V 3
> [[2.7]]
> K 12
> svn:keywords
> V 23
> Author Date Id Revision
> K 13
> svn:eol-style
> V 6
> native
> PROPS-END
>
> As we can see that the sample of dump file contains the current SVN revision number in line [[Revision-number:17]] for the module "fmt​crt" which earlier had revision number [[2.7]] in CVS repository. It also implies that the CVS module "fmt​crt" now has the path [[Node-path: trunk/fmt​crt]].
>
> 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.

In the end it would be best to shift your tools, development model and thinking
to the Subversion revision numbers instead of relying upon CVS numbers. A
short-term pain of switching your tools over to using the Subversion way will be
much better than indefinitely trying to use the CVS model.

Also, what were you going to do when you modify a file and the CVS version
number no longer changes because svn doesn't update that data?

Regards,
Blair

------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=2361712

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

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