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

Building up baseline repository with old builds

From: Jennifer Kesterson <Jennifer.A.Kesterson_at_jpl.nasa.gov>
Date: 2005-10-19 17:01:09 CEST

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

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.

I'd appreciate your help and guidance with this.

To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Oct 19 17:11:12 2005

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.