Rainer Müller wrote:
> Sven Probst wrote:
>> Rainer Müller schrieb:
>>> Don't do this. This will result in a corrupted Working Copy since the folder
>>> should be under version control but is not any more.
>>>
>> If everything in the folder and down in its hierarchy is to be removed
>> from revision control, it is no problem at all to delete the .svn folders.
>> It is the best way to do so, because in this manner all unversioned or
>> changed files can not be deleted accidentally.
>
> Hm, maybe I understand the original question wrong. I thought, Brian want to
> delete a subfolder of his Working Copy. In that case this approach with deleting
> .svn folders won't work.
Just to clarify:
If the folder you want to unlink is isolated and not part of another
working copy, ie its parent folder is not versioned, then you can indeed
just delete the .svn directories. Or you can export and move back. The
folder will still exist in the repository, but your local copy will not
be a subversion checkout, just a directory which contains a snapshot of
that repo state.
If the folder you want to unversion is part of a larger working copy, ie
it has a versioned parent and you want that folder to be ignored and
removed from the repository, then you have to:
1. Export that folder to a safe place.
2. SVN delete it from the parent folder and commit the parent.
3. Move the exported version back to its original location.
4. SVN ignore the folder so that it doesn't get added again.
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
Received on Wed Jul 19 22:57:27 2006