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

Re: Questions on distributed repository layout

From: Ryan Hunt <rhunt_at_hp.com>
Date: 2003-11-25 01:19:31 CET

On Monday, November 24, 2003, at 02:42 PM, Joseph Vigneau wrote:

> Ryan Hunt wrote:
>> I am looking for a solution that will allow Branch development off of
>> Trunk, where each Branch has rapid and total access to its own
>> resources with out restricting I/O for the other Branches, and with
>> out excessive redundancy.
>> Any ideas on this?? Would something like this even be possible with
>> SVN in either its present or future incarnations??
>
> You could use svn:external to segment the tree to different
> repositories, with careful partitioning.

This is not exactly what I am trying to do...

Rather...

Say I have the following

/trunk/common_ancestor

and then do

svn cp svn://host_A/repos/trunk/common_ancestor
svn://host_A/repos/branches/project/common_ancestor

since this is a "cheap" activity it is ideal as project/common_ancestor
receives all the data from trunk/common_ancestor without the overhead.

so what I would like is for project/common_ancestor to be able to
reside on host_B like so

svn cp svn://host_A/repos/trunk/common_ancestor
svn://host_B/repos/branches/project/common_ancestor

yet still have this be a cheap transaction where all the history still
resides on host_A, but all further changes reside on host_B.

-Ryan

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue Nov 25 01:06:55 2003

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.