Menu
The working copy will be located in a directory called trunk on your computer relative to the directory you issued the command in. If you wish to have a different name for your working copy you can add that as a parameter to the end of the command. e.g. This will create a working copy called MyProjectSource .
According to this: http://www.devcha.com/2008/03/svn-directory-svn-containing-working.html
Check-out the folder "blabla" to a different location and then copy its .svn folder back into the original "blabla".
fwiw, I had a similar situation and used svn --force delete __dir__. That solved the issue for me. Then i continued working with my working copy as normal.
What I did to fix this was to delete the local copy of the folder under question and then do an svn update of the parent directly afterwards.
Fixed it right up.
Can you try to check out a new copy of the parent directory?
Edit: To be bit more specific, I meant to suggest going up one level and deleting the containing directory. Then do a
svn update --set-depth infinity
to replace the directory.
I added a directory to svn, then I accidentally deleted the .svn folder within.
I used
svn delete --keep-local folderName
to fix my problem.
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With