Robert Dailey wrote:
> This may be a Subversion issue, but I'm not sure. I'll ask here and
> then if need be I'll forward this on to the subversion mailing list.
>
> When I'm working out of a feature branch, sometimes I will want to do
> an SVN Switch back to trunk, but instead of going to the HEAD of trunk
> I'll go to some extremely early version. In my specific test case,
> doing so results in a folder like C:\IT\work\jewett\vfx\mycomponent
> (Assuming C:\IT\work\jewett is my working copy root) being deleted,
> but the update dialog fails with:
>
> Switch C:\IT\work\jewett to
> http://teamserver:1337/svn/vfxrepo/vfx/trunk, Revision 260
> C:\IT\work\jewett\tools
> Won't delete locally modified directory 'C:\IT\work\jewett\vfx'
> Left locally modified or unversioned files
>
>
> What I believe is happening here is that the entire switch process is
> failing because I have unversioned (but svn:ignore'd) files and
> directories in parent directories that are versioned, but are
> attempting to be removed from the working copy by TSVN. What I would
> expect to happen here is that the switch process does *not* fail here,
> but instead it silently unversions the respective directories that
> contain unversioned items, but does not delete them (Like it does for
> single files), only the .svn folders would be removed. Why is this
> treated as an exceptional error? I don't like that the switch process
> fails because of this. Now my working copy is so messed up that I
> cannot recover it without doing a completely new checkout, or deleting
> some very large directories that cause some expensive bandwidth to get
> back. (such as jewett/vfx directory).
The whole switching is done in the Subversion library. You should ask on
the svn list for help about this.
Stefan
--
___
oo // \\ "De Chelonian Mobile"
(_,\/ \_/ \ TortoiseSVN
\ \_/_\_/> The coolest Interface to (Sub)Version Control
/_/ \_\ http://tortoisesvn.net
Received on 2008-08-27 19:43:47 CEST