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

Re: Best practice for svn repos structure for mutliple release paralllel

From: Les Mikesell <lesmikesell_at_gmail.com>
Date: Fri, 30 May 2008 08:02:53 -0500

Chetan Chatwani wrote:
> Is there any stable utility to migrate data from one svn repos to another svn
> repos with history , like cvs2svn utility ?

svnadmin dump/filter/load, but it would be a one-time, one-way trip
leaving you with a very confusing structure where you can't merge
changes. Normally what you would do is copy to a tag for the release
snapshot and a branch for subsequent maintenance within the same
repository. These will not be affected by any other concurrent work in
the repository but you'll have the ability to merge in updates from the
trunk or other branches if you want.

   Les Mikesell
To unsubscribe, e-mail: users-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: users-help_at_subversion.tigris.org
Received on 2008-05-30 15:03:24 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.