[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

RE: Partial working copy relocation

From: Bob Archer <Bob.Archer_at_amsi.com>
Date: Fri, 23 Jul 2010 15:43:03 -0400

> On Fri, Jul 23, 2010 at 22:38, C. Michael Pilato
> <cmpilato_at_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.

I think the biggest problem here is that the working copy "root" doesn't necessarily equate to the project "root" or any logical root. So, someone could have checked out a sub-folder of a project and while that becomes the working copy "root" it isn't the project "root".

Tools like git and hg make it pretty obvious what the root of a project/repository is. Basically everything happens in reference to the root folder of the repository no matter what your pwd is. For example, a merge happens in the full repo not just the sub-folder you are in.

Are there any plans to have some way to indicate a "project root" in svn 1.7? Or, will it work the same way... we will know the working copy root but not necessarily the project/repository root. Having this might help with sub-tree merges as well as the relocate issue being talked about above.


Received on 2010-07-23 21:43:42 CEST

This is an archived mail posted to the Subversion Dev mailing list.