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

RE: Migration to SVN

From: Giulio Troccoli <giulio.troccoli_at_uk.linedata.com>
Date: Fri, 11 Dec 2009 15:29:11 +0000

>

Linedata Services (UK) Ltd
Registered Office: Bishopsgate Court, 4-12 Norton Folgate, London, E1 6DB
Registered in England and Wales No 3027851 VAT Reg No 778499447

-----Original Message-----

> From: barveaniketan_at_gmail.com [mailto:barveaniketan_at_gmail.com]
> Sent: 11 December 2009 13:20
> To: users_at_subversion.tigris.org
> Subject: Re: Migration to SVN
>
> Hi All,
>
> I am also working on a big project to migrate our source code
> from an old system (CMS running on VMS OS) to Subversion.
>
> So could you please tell me what process you have followed
> for CMS to SVN MIGRATION?
>
> I want know below mentioned points.
> 1. How CMS data is exported to local directory. In my case I
> have around 1000 elements do take copy of each element
> manually its very time consuming & critical job.

We had perl scripts to work with CMS so I never knew the direct CMS commands. However, we worked with classes which I think *are* CMS specific. How to use them in your case it much depends on how you have organised your code I think.

> 2. Suppose once you have exported data to local directory.
> Then what is the procedure to export data to the subversion.

You can use a series of "svn import" or maybe just one and then some "svn copy" and "svn commit". Again it depends on how your code is organised and how you want it organised in Subversion.

Giulio

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

Please start new threads on the <users_at_subversion.apache.org> mailing list.
To subscribe to the new list, send an empty e-mail to <users-subscribe_at_subversion.apache.org>.
Received on 2009-12-11 16:30:22 CET

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.