On Tue, Jan 08, 2013 at 09:56:26AM +0100, Johan Corveleyn wrote: > Well, cross-wc.db commits are certainly supposed to work since 1.7: > > - issue #2381 [1] (Cannot commit multiple WC paths which lack a common > parent directory), fixed in r1091928 by Bert. > > Does that mean cross-wc moves should work? I think they do in 1.7 > (some of my colleagues do this sometimes, when they move some code > from module A to module B, and they don't have the common parent > directory checked out, but just the two disjoint working copies). > > If they work in 1.7, it would certainly be desirable to keep them > working (with the "movedto" support) in 1.8. And if they don't already > work in 1.7, well, that would be a nice enhancement then :-).
That'ws probably not going to be possible for 1.8, sorry. I think adding such a feature to the existing move implementation now would simply take too much time. Perhaps in a later release. Even then, it would require us to run sqlite queries across multiple databases, so I'd rather wait until several working copies can share a single wc.db, and then address this issue. As a workaround, your colleagues can use 'svn copy' and 'svn delete'.
