On 22.07.2015 02:41, Nico Kadel-Garcia wrote:
> On Tue, Jul 21, 2015 at 3:58 AM, Andreas Stieger <andreas.stie...@gmx.de> 
> wrote:
>
>>> Even if you have two repositories that are identical to each other, one of 
>>> them will need to be designated the "master", and that will be the one that 
>>> all commits are made to.
>>>
>>> Subversion is a one-central-repository system.
>> Unless of course one of the lesser known features is used:
>> Cross-repository copies and merges actually work (to not use the term 
>> "supported"). Copies/moves will become additions, inter-revision history is 
>> compessed and there is no merge tracking. See the three-agrument (copy or) 
>> merge syntax "svn merge A@N A@M .", where A and "." refer to different 
>> repositories.
>>
>> Not that it's recommended in the user's case, but it should be mentioned.
>>
>> Best approach in the svn space for Mani would be vendor branches based on 
>> the information shared.
> Or investing in a genuine multi-master version of Subversion, which
> Wandisco sells. Simply spending some money instead of investing in
> hours of hacking and refactoring to make things work for your own
> special needs is sometimes.... well, more expensive in other ways.

I have trouble understanding why you keep plugging for SVN MultiSite on
this list. Have you ever actually used it?

-- Brane

Reply via email to