On Fri, Mar 2, 2012 at 10:47 AM, Geoff Hoffman <ghoffman_at_cardinalpath.com>wrote:
> Yeah I was just reading this:
>
> "By default, the aforementioned basic requirements of a mirror are that it
>> allows revision property modifications and that it contains no version
>> history. However, as of Subversion 1.7, you may now optionally disable the
>> verification that the target repository is empty using the
>> --allow-non-empty option. While the use of this option should not become
>> habitual (as it bypasses a valuable safeguard mechanism), it does aid in
>> one very common use-case: initializing a copy of a repository as a mirror
>> of the original. This is especially handy when setting up new mirrors of
>> repositories which contain a large amount of version history. Rather than
>> initialize a brand new repository as a mirror and then syncronize all of
>> the history into it, administrators will find it *significantly* faster
>> to first make a copy of the mature repository (perhaps using *svnadmin
>> hotcopy*) and then use *svnsync initialize --allow-non-empty* to
>> initialize that copy as a mirror which is now already up-to-date with the
>> original."
>
>
>
> Now here's the interesting part. I'm running svn 1.6 on the source repo,
> 1.7 on the mirror repo... (I think)
>
>
If the svnsync command you use is from 1.7.x it will work. Does not matter
what version the server you are synching is running.
--
Thanks
Mark Phippard
http://markphip.blogspot.com/
Received on 2012-03-02 17:06:10 CET