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

Re: Converting from VSS to SVN

From: Frank Gruman <fgatwork_at_verizon.net>
Date: Fri, 26 Sep 2008 00:31:20 -0400

On Thu, 2008-09-25 at 20:31 -0500, Ryan Schmidt wrote:
> On Sep 25, 2008, at 16:21, Alain wrote:

> > Do I have to
> > - first copy all files of my local directory in a temporary one,
> > - then delete these files,
> > - export the files from the SVN repository (they come from VSS),
> > - replace them with the contain of the temporary files
> > - finally check in to take the modifications into account
> >
> > Or is there a more simple way to check in my files in my new SVN
> > repository where VSS projects have just been imported ?

With a few assumptions, I think you want this:

(Assumption 1) Your files all exist in some fixed location on your
machine for build dependencies, and that location currently has your
'old' source files. If not, you could just start at step 3.
(Assumption 2) Your posting said you had already migrated from VSS to
SVN, so we assume you have a working repository.

Step 1 - As you said, copy those files out to a safe location to avoid
anything being overwritten.
Step 2 - Delete the files and folders in that hierarchy to make the
folder structure clean.
Step 3 - Check out the existing files from Subversion into your desired
file location.
    - You should now have a functioning working copy.
Step 4 - Copy the previous files over top of the working copy.
Step 5 - Check in the working copy either as one large commit, or (even
better) commit them as logically grouped changes for better record
keeping

Hope that helps!

Regards,
Frank

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: users-help_at_subversion.tigris.org
Received on 2008-09-26 06:32:02 CEST

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.