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

Re: Slave repository

From: Stefan Langer <mailtolanger_at_googlemail.com>
Date: 2007-01-25 10:50:47 CET

Shem Page wrote:
> Yes I had found some posts on the net which referred to SVK, which is
> how I started thinking about a master slave solution, unfortunately I
> wasn't aware subversion doesn't support such concept. Even less
> fortunate is the fact that we must use subversion, as that is what is
> already in place in our partners environment.
> Is there another way around this problem. Can we simply import our work
> into a branch on their repository and force a merge? The problem about
> that idea is I don't think subversion would be able to manage the merge
> because it would be seen as two different projects.
> Ideas?
As you said it yourself, subversion itself is not designed for a
distributed environment (unless you need readonly slaves then you can
use the new sync tool provided by 1.4) so you should clearly state that
to your partner and propose either to use a thridparty tool (like SVK)
on top of subversion or find a different version control system that is
capabale of doing what you want.
A third option is to write your own hooks to move commits to the
appropriate places.


To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Jan 25 10:49:00 2007

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.