I am learning how to use SubVersion at the moment.  I am a very long time VSS user and have finally been convinced (by poor behavior from Visual Source Safe, not its opponents) that it is not adequate for source control.

While attempting to migrate from VSS bindings in Visual Studio 2005*, I tried to "add solution to repository" but I navigated to the wrong place.  Fortunately, nothing happens on the server until you commit.  Win #1 for SubVersion. 

( *Visual Studio 2005 is a fantastic product, just to be impartial )

Unfortunately, my folder was now a working directory for the root of my source control repository.  After failing to find easy instruction as to how I can "undo" my improper repository binding, I came to the assumption that deleting the magic _svn directory might cause subversion to forget what I had done.  I wouldn't recommend this in the midst of a project under source control but if you've added a project wrong and not yet commited, I see no risk.  So...

1. Use windows search (or your favorite desktop search) to recursively locate all directories named "_svn" from the root of the windows directory you would like to disassociate from subVersion. 
2. When search returns with your list, delete every _svn directory shown.  Make sure you are locating hidden files, these directories are marked hidden.

It worked!  The little icons all disappeard from the folders and I could open the project in Visual Studio with no issues. 

Time to try again!

I entered the url to the correct directory in my subVersion repository and checked the "create sub directory" check box.

An error!  It can't find the folder it created.  Repeat step1.  I think I'll try another approach...  more to come