On Aug 16, 2006, at 09:15, Olivier Sannier wrote:
> I have the following situation:
>
> One main and public server onto which there is the current
> development version. I have no control on the configuration of this
> server. Let's call it A.
> One secondary and personal server onto which I want to do some
> development that I intend to put on the public server at some point
> in time. I have full control of this one. Let's call it B.
>
> I have done an export from A/trunk to a local folder (c:\prog
> \privatedev\) and I have added this content to B/trunk.
> I'm doing my development in this local folder, but in order for the
> local repository to only contain the changes to go from A/trunk to
> B/trunk, I'd like to regularly do an update from A/trunk.
> I know about feature branches and the merge ability to specify URI,
> but in this case, it does not work as it says that the local
> repository does not match the URIs.
> What would you recommend me to do in order to have those regular
> sync points?
> Right now, I'm thinking of writing down the last revision from A/
> trunk I updated B/trunk to (rXX), use merge to get the unified diff
> from rXX to HEAD in A/trunk and apply those diffs to B/trunk. But
> this is quite a manual process and I'd prefer to have a more
> automated one.
I don't think Subversion is designed for this multiple-repository
kind of setup. You may want to look into SVK, which is, and which is
built on Subversion:
http://svk.elixus.org/
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Aug 16 14:30:45 2006