I think we should fall back to this scenario if we can't keep the move
tracked, instead of just not trying at all for these users at all.
This way those clients that must stay compatible for their users can at
least try to use the new feature instead of always do the dumb thing.
Bert
From: Greg Stein [mailto:gst...@gmail.com]
Sent: dinsdag 8 januari 2013 14:43
To: Bert Huijben
Subject: Re: mixed-revision moves (Re: 'svn mv' between disjoint wc's of
disjoint subtrees)
On Jan 8, 2013 6:09 AM, "Stefan Sperling" <s...@apache.org> wrote:
>...
> What I suggest is that we revv the move API before release, and keep the
> old one around without any move tracking. I.e. we'll keep existing API
> users working as they do now, but force new API users to rethink their
> approach (or simply catch and handle the error) when they start using 1.8.
+1
Great approach.
Cheers,
-g
