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

Re: installing SVN after development has started

From: Ryan Schmidt <subversion-2007a_at_ryandesign.com>
Date: 2007-01-18 19:36:48 CET

On Jan 18, 2007, at 11:57, Stephen Winnall wrote:

> I'm new to Subversion and I'd like to start using it for some
> projects which have already been under development for
> some time. I have copies of the original files for the projects
> and would like to put these into the repository as the initial
> version and then take the current status and load it as a
> subsequent version on top of the initial version,
> I've no doubt this question has been asked many times before
> (and I apologise for that), but I haven't been able to find the
> right combination of keywords to make the mailing list archive
> or Google spit it out, and I have a similar problem with the Book.
> Could someone please point me at what I should be reading
> or give me a hint as to what terms I should be looking for.

You should be looking into the svn_load_dirs.pl script which is
included with the Subversion source distribution. Basically, you will
"svn import" the initial version as your trunk. Then you will
(probably want to) tag that version of trunk. Then you will use
svn_load_dirs.pl to update the trunk and tag it again, with each
subsequent iteration of the project that you have on hand. For
example, when I started using Subversion, I had about 20 older
versions of my project that I could import in this way.

I recently suggested this for someone else. See my answer to his
question #4 in the message after this one:


Read the chapter in the book on vendor branches for more on

To reply to the mailing list, please use your mailer's Reply To All  
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Jan 18 19:37:23 2007

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.