Over at infra@ we ran into an issue where an 'svn mv' between two
disjoint working copies --- each wc is of a different subtree of trunk
--- became a mv without history.  I couldn't reproduce that one with
a 1.8-dev build.  However, I ran into an issue with 'status' handling
such moves:

% $svnadmin create r  
% $svn mkdir -qmm file://$PWD/r/{foo,bar} 
% $svn co -q file://$PWD/r/foo
% $svn co -q file://$PWD/r/bar
% touch foo/iota; $svn add -q foo/iota; $svn ci -qmm foo/iota
% $svn mv foo/iota bar/kappa 
A         bar/kappa
D         foo/iota
% $svn st -q foo bar 
D       foo/iota
        > moved to foo/kappa
A  +    bar/kappa

This output appears to be wrong: the 'moved to' is wrong because the
move destination is ^/bar/kappa, not ^/foo/kappa; and the "moved from"
output is completely absent.

Reply via email to