On Oct 19, 2005, at 17:01, Jennifer Kesterson wrote:
> Hello,
> I hope this hasn't already been asked and answered a million times
> but I wouldn't know where to begin to search for this in the
> archives, so here goes.........
>
I had to ask too when I need to do this for a project some months
ago. :-) It's not the easiest thing to search the archives for.
> We're a new project but we've already completed some builds. We
> didn't have a formal CM system set up for those builds but we are
> preparing Subversion for use before the next build.
>
> We'd like to establish our baseline in the Subversion repository by
> importing Build 1.0, then adding 1.1 on top of that, then 2.0, then
> 2.1, and tagging each one after it is imported, so that the end
> result is a repository that looks as if we had been using it from
> the beginning.
>
> What is the best way to do this? I'm a relatively new user and
> from my limited experience I know that importing Build 1.0 and
> tagging it will be easy. From there, how do we import the
> subsequent builds on top of that? Is it possible? If not, then
> I'm wondering if we could import build 1.0, tag it, then import 1.1
> into a separate tree and tag it, then do the same with 2.0 and 2.1,
> then import the current set of development code into the main trunk
> and continue from there.
Read all about the svn_load_dirs Perl script that's in the contrib
directory. It's designed for loading third-party libraries into your
Subversion repository, but it works just as well for importing your
old builds.
The version included with Subversion doesn't handle symlinks, but
there is a patch that adds symlink support if you need it, which also
worked great for me.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Oct 19 19:02:10 2005