Re: Initial Move Support in /trunk now
From: Julian Foad <julianfoad_at_btopenworld.com>
Date: Mon, 23 Sep 2013 14:40:54 +0100 (BST)
Stefan Fuhrmann wrote:
Cool! Thanks for starting the implementation, Stefan.
> It turned out that move() should not implicitly issue a delete()
Well, we know that ordering of moves is a tricky issue.
> and, worse, makes it hard to verify incoming changes.
I don't understand what you mean there.
> Instead, just call move() as you would call copy() today and
OK, so the API is currently structured the same as copy-and-delete except the copy part is explicit designated as a "move". Fair enough, for now.
> As of r1525467, there 'svn log' now supports all moves across
> Currently, 'svn log --stop-on-copy" does not follow moves, yet
This is an archived mail posted to the Subversion Dev mailing list.