How to recover a working copy after switch

Hello,

I'm seeing several cases where an svn switch does not
complete normally, leaving the working copy in a state
where many folders show up in Switched status.

Update doesn't seem to help; switching again doesn't
seem to help...

In addition, I saw one case where the project's root folder
had its .svn subfolder deleted (probably by developer
error), at which point commands issued from the root
folder resulted in the expected '. is not a working copy'.

I have tried a checkout -N of the root folder, and although
that does restore the svn metadata, it leaves the rest of
the project looking unversioned.

I'm trying to avoid using the checkout command each
time a working copy looks a little funky. But the cases
above have stumped me. Are there specific techniques
or best practices that can address these?

I realize I have not reported a specific failure here. I am
looking for general advice, perhaps variants of the commands
which I have not tried yet. My theory is that after a while,
doing development across trunk and private branches,
the working copy, for whatever reason, will fall ill. What then?

Thanks,

Walden Mathews

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue Oct 26 21:08:01 2004