Ben and I recently started producing a functional and UI spec for local moves:
<https://wiki.apache.org/subversion/LocalMoves> We need this in order to test the sub-features against a known goal, and we need it in order to produce software that has consistency. Please join in with the thinking and writing. There's quite a big conceptual change to be addressed, because now that we have local moves we can no longer assume that every path refers to "a node" and that every node has "a path"; now some nodes live at two paths in the WC (at one path "now" and at another path "before"). After trying to decide what various subcommands should do when given the path of one side of the move, and seeing that we have no consistent plan there yet, I wrote in the Wiki: "We need to go beyond simple path-based addressing now that we have 'move', because it affects two paths so we can't continue to assume a model where a path simply addresses 'the node' and a node has 'a path'. Idea: 'to' path identifies the move; 'from' path identifies any replacement at that path???" - Julian -- Certified & Supported Apache Subversion Downloads: http://www.wandisco.com/subversion/download
