[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: Chetan Chatwani <chetan_at_savvion.com>
Date: Fri, 30 May 2008 01:59:56 -0700 (PDT)

Is there any stable utility to migrate data from one svn repos to another svn
repos with history , like cvs2svn utility ?

Ryan Schmidt-33 wrote:
>
> On May 30, 2008, at 01:15, Chetan Chatwani wrote:
>
>> We are having going to have 2(8.0 and 7.5) release parallely.
>> Should we
>> create :
>> - mutliple repos for each release or
>> - create one repos and in that have branch for short cycle
>> release(7.5) and trunk for major cycle release(8.0). This trunk
>> will be
>> carried for future releases also such as 9.0 etc.
>
> You can't merge or branch or copy between repositories, only within a
> repository. So you will definitely want to have a single repository
> with as many branches as you need.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe_at_subversion.tigris.org
> For additional commands, e-mail: users-help_at_subversion.tigris.org
>
>
>

-- 
View this message in context: http://www.nabble.com/Best-practice-for-svn-repos-structure-for-mutliple-release-paralllel-tp17552301p17554467.html
Sent from the Subversion Users mailing list archive at Nabble.com.
---------------------------------------------------------------------
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 11:00:23 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.