On Mon, Feb 22, 2010 at 3:31 PM, Olivier Sannier <obo...@free.fr> wrote: > Hello all, > > Let's say we have the following repository: > > /trunk > /trunk/bin > /trunk/sources/report_engine/models > > and an external on bin defined as the following: > > ../sources/report_engine/models models > > so when I checkout trunk, I get a copy of > /trunk/sources/report_engine/models inside the bin/models folder. > This is very convenient to have "symbolic links" inside a repository. > > Now I do this: > svn cp /trunk /branches/test > > then I modify a file inside /trunk/sources/report_engine/models and commit > it. > Finally, I want to work on the branch and switch my working copy to it: > > svn switch /branches/test . > > While it updates my working copy to match all the changes made into the > branch, it never updates bin/models to represent the content of > /branches/test/sources/report_engine/models > > I reread the svn book and it is not clear to me whether or not svn switch is > supposed to update a relative external. > To me it would be quite logical that it would, hence my surprise when I saw > the above behavior. Could it be that I missed something obvious?
I think this is a known bug. See http://subversion.tigris.org/issues/show_bug.cgi?id=3390 It was recently fixed and proposed for backport to 1.6.x. It will probably, hopefully, most likely, ... be included in 1.6.10. Johan
