Re: Remove control

Sven Probst wrote:
> After removing the .svn directory its parent directory (let's call it
> "DirA") is no longer under version control, it became a "normal" folder.
> If this folder "DirA" is a subdirectory of a working copy, the working
> copy now seems to be defective to Subversion if you try to update,
> because the folder "DirA" is in the repository but not in the working
> copy as versioned folder. To solve this problem remove "DirA" from the
> repository, too. You can use the repository browser to do so. Now the
> folder "DirA" is missing in the repository and no versioned part of the
> working copy - SVN shouldn't have a problem any more.

No, please don't do that. You should never change or remove the .svn
directory. You can get away with it in a single level hierarchy, but not
in subfolders.

Firstly, to recover from the obstructed state, remove the Build folder
completely, then update the parent folder.

If you want to keep the Build folder and its contents, first export it
to a temporary location. As these are generated files, you probably
don't need to bother.

TortoiseSVN->Delete the Build folder and commit.

If you exported the Build folder, you can now bring it back as an
unversioned folder. Or do another build and recreate it.

TortoiseSVN->AddToIgnoreList the Build folder and commit.

Simon

-- 
        ___
   oo  // \\      "De Chelonian Mobile"
  (_,\/ \_/ \     TortoiseSVN
    \ \_/_\_/>    The coolest Interface to (Sub)Version Control
    /_/   \_\     http://tortoisesvn.tigris.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: users-help@tortoisesvn.tigris.org