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

Re: Best way to import old project?

From: Ryan Schmidt <subversion-2005_at_ryandesign.com>
Date: 2005-04-04 03:52:23 CEST

On 04.04.2005, at 03:18, Robert Mohr wrote:

> Assuming that all branches and tags have the same files (but different
> content in those files), you can import the trunk, svn copy it to each
> of the branches and tags, and then, without using svn, replace each
> branch and tag in the working copy with what you actually want in it.
> svn should recognize that the branch is roughly similar to the trunk,
> and that will keep your copies "cheap". If a file is in the trunk but
> not the branch/tag (or vice-versa), you'll need to remove it using
> 'svn delete', or add it with 'svn add'.

It doesn't seem like that'd be practical in this case, since 1.1 has a
drastically different assortment of files than 1.0, and 1.2 has a whole
different set of filename changes and additions. This project is a web
site. Basically, the change from the 1.0 to the 1.1 line was a
reorganization of the database, which changed which database access
files were used, and the change in 1.2 was using a template engine for
the HTML, which had a major effect on the file and directory structure.

Also, although there may be some new releases of the 1.0, 1.1 and 1.2
lines, the goal within the next few months is to get the new 1.3 to the
point that it can be deployed on all systems, at which point we can
pretty much forget the 1.0, 1.1 and 1.2 branches. But it might still be
good to have the history.

Any other suggestions?

To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Mon Apr 4 03:55:02 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.