Over in another thread[1], a question was raised about the behavior of 'svn switch --relocate' today. Namely, if you run 'svn switch --relocate' on a subdirectory of a working copy (that is, *not* a "working copy root"), what should the behavior be?
The behavior today is that the subdir and its children -- and only the subdir and its children -- will be relocated. On the one hand, this is what you'd expect because Subversion has historically avoided operating on the parents of operational targets. On the other hand, is there ever a case where the events that force someone to relocate a subdirectory of their working copy do not also apply to the parents of that subdirectory? Should such commands relocate the whole working copy, from its root down? Should they simply complain that you've not targeted the root of the working copy, and prescribe doing exactly that? Should the code behave as it does today? -- C-Mike [1] http://svn.haxx.se/dev/archive-2010-07/0438.shtml, http://svn.haxx.se/dev/archive-2010-07/0439.shtml -- C. Michael Pilato <cmpil...@collab.net> CollabNet <> www.collab.net <> Distributed Development On Demand
signature.asc
Description: OpenPGP digital signature
