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

RE: Importing multiple revisions

From: Crucius, Wesley <WCrucius_at_sandc.com>
Date: 2004-04-16 05:35:29 CEST

Before you give up on a complete import, check out perforce. There is a
version that allows a limited number of users that's free. Perforce can
import VSS and there are scripts out there to import from perforce to
subversion. I have not tried this, but I've read of others that claim
it works...

        -----Original Message-----
        From: Ray Johnson [mailto:Rayj@ingenio.com]
        Sent: Thursday, April 15, 2004 9:37 PM
        To: users@subversion.tigris.org
        Subject: Importing multiple revisions
        I'm currently working on how we can import our large VSS
repository into Subversion. We do not want to do a full migration as we
really do not need all the old history added (and it has proven to be
extremely difficult to do). So instead we would like to import the last
few "releases" of our code into Subversion.
        Importing the oldest release is very easy. It will simply
become my "trunk" and I'll also make a copy that will basically be the
tag for that release.
        I now want to "import" the next release. When finished the
second release should be what is in my "trunk". I realize this doesn't
provide a "true" history. In in VSS we renamed a file it would show up
in SVN as a completely new file and the old file being deleted. That is
fine with us as people can always go back to VSS to find out what really
happened (which will only happen rarely and only for a few months).
        So in the end we would have history through the past couple of
release - but only the final files in each release. But moving forward
we would have a normal SVN repository.
        However, I'm not sure of the best way to do second (and
subsequent) "imports". Does anyone have any ideas how this can be done?
        The obvious solution is to get a working directory of my trunk,
make the working copy look like the second release and do a commit.
Unfortunately, this is a bit more complicated then I first envisioned.
I can't just do a file sync - because for added/deleted files I actually
need to do svn commands. We are talking thousands of files here. (Over
1700 directories.) So I'm really hoping I can find a better solution.
        Maybe I can import the second release into a separate space and
merge it into the trunk? This sounds like the right way to go but I
haven't thought it through... Any way, has anyone else done this? Any
Received on Fri Apr 16 05:36:17 2004

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.