On Tue, Feb 07, 2012 at 06:26:54AM +0900, Hiroaki Nakamura wrote:
> 2012/2/6 Stefan Sperling <stsp_at_elego.de>:
> > 2) Do something else that effects repositories, too, and provide
> > a clean upgrade path for everyone (servers and clients).
> > AFAIK nobody has made a suggestion as to what could be done here.
> What do you mean by a clean upgrade?
> Is it clean if we do dump and load for repositories and re-checkout for
> working copies?
Yes, this is what I meant. I listed earlier in this thread what
the acceptable upgrade paths are in terms of our compatibility
So, the bottom line is that there is more work that needs to be done
than you've done so far to get this problem fixed. I realise that this
may be frustrating for you, and I hope that you don't give up but try
to work towards a solution that does not harm compatibility.
Please understand that we're trying to find the right balance for our
user base. Some users have the problem you want to fix, and others would
run into compatibility problems if we fixed it by applying your patch.
This is not an easy tradeoff to make for us. I would prefer if Subversion
didn't have this stupid problem on Mac OS X. But so far we have never
compromised compatibility and this is a very important property of Subversion
that we do not want to lose. Compatibility is a high priority for us.
Received on 2012-02-06 23:22:38 CET