On 9/14/06, Duncan Murdoch <murdoch@stats.uwo.ca> wrote:
> On 9/14/2006 2:38 PM, Garrett Rooney wrote:
> > On 9/14/06, Mark <mark@mitsein.net> wrote:
> >> I am curious aboyut this new feature. I have a custom solution in
> >> place to keep repositories synced between two servers, one bein the
> >> master and one being the standby. I can switch roles between servers
> >> as well. From my first read of what info their is about svnsync, it
> >> sounds like the destination repository is only ever meant to be
> >> read-only. Is that a hard and fast rule? Is there something I could
> >> do to switch the roles of destination and source repositories?
> >
> > It's not a hard and fast rule, but to switch which repos is the master
> > and which is the slave you'd have to manually go in and mess with the
> > svnsync revprops on r0 of whichever is the slave. It's definately a
> > hard and fast rule that you can only have one master at any given
> > time. If you write to both the slave and the master then there's no
> > mechanism for resolving the inconsistency.
> >
> >> A HOWTO for new features like this will help a lot. I'm willing to
> >> write it with some help from the devs that put this feature together.
> >
> > Paul Querna put up a HOWTO for basic read-only mirroring on his blog yesterday:
> >
> > http://journal.paul.querna.org/articles/2006/09/14/using-svnsync
>
> Is there other documentation online somewhere? That page lists the
> how-to, but not the things you can do with the sync'd copy.
There's not a whole lot of documentation yet, but as far as "what you
can do with the sync'd copy" I'm not sure what you're looking for.
You can do anything with the copy that doesn't involve writing to it.
Well, actually, you can write to it, but only if you never want to
sync it again.
-garrett
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Sep 15 01:50:02 2006