> Actually, instead of making it an 'svnadmin' command, would you care to
> make it its own command (E.g. 'svnobliterate')? Or at least make it so
> that it has no shortened form (E.g. 'co' is short for 'checkout')?
I like the idea of making it its own command. It should also be
hook-script protected like revision properties are. If you don't have
a hook script set up to specifically allow the obliterate to take
place, then you're not allowed to obliterate anything. This would also
allow you to log the obliteration if you so chose. It seems like it
would also make sense for the hook script to have access to a dump of
the data being obliterated, so it could create a backup that could be
loaded back into the repository if need be.
>
> I keep looking at it and it just keeps feeling like a very big nuke...
I have to agree with you there. I like the term "obliterate" for that
very reason. It makes the command sound just as scary as it really is.
-Bill
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Mon Jan 31 19:45:38 2005