I have hashed this out on the users list: http://subversion.tigris.org/servlets/ReadMsg?list=users&msgNo=71601 Here is the summary as best described by Steven Bakke: "Let's say I want to take a look at what is in another tag for one of my subdirectories: % cd <work> % svn switch <tag-URL> <work>/A (Look at the files and do whatever. No modifications) Now lets say I want to switch back to trunk, since I'm done looking at whatever was in that tag. % svn switch <trunk-URL> <work>/A When 'A' had been deleted from trunk in the interim, there is no way to do this. In my opinion, this is a flaw in subversion. Regardless of whether you understand the reasoning for it, I believe you should always be able to "undo" a switch successfully. I'm thinking this is somewhat related to the "depth" issue being dealt with in 1.5. Once a directory becomes part of the current working copy, it is impossible to remove it." Mark Phippard suggested (outside the mailing lists): "I'd suggest using switch (now that it has peg revision support) to switch C to a revision where it still existed in trunk. Then use svn update on its parent which will remove it." But I contend that this is not a valid general solution - imagine the wasted time & bandwidth to update some ridiculously large set of data just to delete it again! I guess I'd like to see something like --force to force a deletion of the path from your working copy if the target url does not exist assuming no modified data (of course). Any other suggestions would be most welcome!
Original issue reported by emiller