On Fri, Jul 23, 2010 at 22:38, C. Michael Pilato <cmpil...@collab.net> wrote: > 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. > +1.
> 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? My opinion that best way is forbidding relocating subdirectory working copy, since it's proven to broke parent working copy. As far I remember we have the same behavior for svn upgrade now. -- Ivan Zhakov VisualSVN Team
