Strictly speaking, the dialog "Delete Unversioned Items" (reachable
via Revert) does exactly what its title says. However, it would be
more useful if it took into account the svn:ignore information.
My use case is this: I want to make sure that there are no source code
files in my project working directory that are not under version
control (for example, this can happen if you merge from another
branch, then undo the add operation). The "Delete Unversioned Items"
dialog lists these files, but it also lists the following groups of
1) Files/folders which are ignored by SVN (thanks to svn:ignore)
2) Files/folders *inside* ignored folders (one or more levels below
the ignored folder). Let's call these "recursively ignored".
Now consider that my project has around 50 modules, each with its own
(versioned) subdirectory. Each of those has the following structure:
.classpath (ignored file)
.project (ignored file)
.settings (ignored folder)
org.eclipse.jdt.core.prefs (non-versioned file inside
org.maven.ide.eclipse.prefs (non-versioned file inside
target (ignored folder)
classes (non-versioned folder with hundreds to thousands
of generated class files in a deep hierarchy)
Due to the large number of ignored files and the myriads of
unversioned files that are "recursively ignored", the "Delete
Unversioned Items" dialog fails to address my use case.
I therefore propose that a checkbox is added to the dialog. If
checked, the item groups 1) and 2) mentioned above are left out from
the list (it might also be split into two separate checkboxes).
Probably, it should be unchecked by default.
What do you think?
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2012-01-11 15:02:22 CET