On 17 jan 2013, at 20:59, Julian Foad <julianf...@btopenworld.com> wrote:
> Ben and I recently started producing a functional and UI spec for local moves: > > <https://wiki.apache.org/subversion/LocalMoves> I think the table in the wiki provides a well needed overview. If nothing else, it demonstrates the the amount of points of interaction with other commands. I don't have the knowledge to comment on some things, but I have a lot of interest in seeing move materialise. There was nothing in the wiki page that I have any issues with. > Idea: 'to' path identifies the move; 'from' path identifies any > replacement at that path???" That makes a lot of sense, especially considering replace. Also, it somehow feels consistent with how copy works today (the to-path is key). That should not be a constraint, but still important for end user adoption/understanding. Regarding revert and --force: Yes, I think --force should be required to break the move into copy/delete. It would otherwise become one of those incredibly annoying mistakes. - If both to-path and from-path are included on svn revert, perform revert of the whole move. No force required. - If from-path has been replaced, the move can not be reverted. The replace must be reverted before (i.e. reverse order to how they were moved). - If either from-path or (exclusive) to-path is included, require force to break move into copy/delete. Most of this was just rephrasing of the wiki, except the suggestion to revert the move if both sides are included in the command. Good stuff, Thomas Å.
