Max Bowsher wrote:
> The need to keep our basic command set small, to avoid svn becoming daunting
> to new users, and making the learning curve intolerably steep, is not a new
> issue.
>
> I agree with it, but taken alone, it stops us adding useful utility
> subcommands - the sort of thing I am thinking of:
> svn purge: Remove unversioned files from a WC
Out of curiosity, what's the purpose of that?
I've done something sligthly similar, in order to clean up a working
copy to make it look like it did when I checked it out. Sort of like
'make clean', only using SVN to tell me what's source code and what's
compiler output.
Specifically, it removes files that are svn:ignore'd as opposed to
files that are not versioned. Thus it keeps any files and
modifications you've added to the WC yourself.
(Python script attached.)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Fri Nov 4 13:53:16 2005