Question

I just had a problem with a tree conflict in subversion/tortoisesvn. after a lot of faffing about, reverting and clean ups, it got into the state where one existing subtree was shown as “added” (there was no _svn directory inside it), even though the subtree was identical to the repository. so I deleted that subtree thinking an update would bring it back again

however, to my surprise, update doesn’t bring this directory back and the commit and check for changes windows both imply that I am completely up to date.

of course i can just checkout a new working copy so i’m not that worried about rescuing it, but my concern is more that I currently have a working copy that I know has a big chunk missing but the tool seems to think is fine. this doesn’t seem very good for a version control system, and I’m worried about the consequences if this happened again in future without my noticing it.

is there any tool i can use to force a complete re-scan of my working copy, or to spot these kind of inconsistencies?

thanks

Andy

Answer 1

Try using the “update to revision” command, then set the update depth to “fully recursive” in the dialog.