Sven Brueggemann wrote:
>> - On a related note, a menu item to remove svn from a folder (ie.
>> > delete all the .svn sub-folders) would be nice. It's easy enough to
>> > do but I think a menu option would still be nice.
>
> I don't think that's a good idea, since you never should remove
> the .svn folders of subdirectories in a working copy. If you want
> a clean copy of your files without .svn folders, use the Export
> command.
But Export can take a lot of time and disk space if there are a lot of
ignored (build) files, and it fails if the working copy contains NTFS
reparse points on Windows, and maybe if it contains (symbolic) links or
devices on Unix-like systems. Obviously such special files/folders are
unversioned, but is there a reason to disallow them from a working copy?
In any case, I agree users shouldn't be messing with .svn folders, but
surely there should be able to remove them and reclaim disk space.
Forgive me my ignorance, but I don't think there is anything doing that
in SVN nor TortoiseSVN? For instance, to delete an entire working copy
and all of its unversioned contents, you simply delete the directory,
right? This removes .svn folders (along with any other folders) from
the working copy before zapping it entirely, so should not be done...
Okay that was twisting words, but I really think there is a case for
safely removing .svn directories. Starting with Daniel's suggestion and
appending 2 operations I have been looking for:
- "Degrade to normal folder": remove all .svn directories from a working
copy. Looking at discussions on the web, it seems the most wanted
feature. I guess for command line SVN users, the answer "just remove the
.svn directories" is simple enough.
- "Safely reclaim diskspace": remove all .svn folders and all committed
files; i.e. subtract from the directory everything that would be
restored if you checked the revision out again.
- "Aggressively reclaim diskspace": just delete the entire folder with
the working copy. But instead of warnings about read-only files
.svn/.dir-props-base and so on in the middle of the performance, explain
what is about to happen up front.
To start, this should be done on the working copy itself, not on a
subdirectory. With a warning if versioned files were modified. The
more I think of it, the more I see these methods as one, along the rest
of the excellent interface: offer a list of all items about to be
irreversibly deleted, with checkboxes. Maybe I should try to program it
myself. Not soon though.
--
Stein
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: dev-help@tortoisesvn.tigris.org
Received on Tue Aug 22 19:50:35 2006