William Nagel wrote:
>> 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.
Considering the most likely reasons for using the command
(legal/copyright/patent related and accidentally added huge files) I
doubt a lot of people will want to keep backups of what they obliterated...
Anyway, I think a complete repository backup or dump from before the
obliteration would be a better way to undo the obliterate.
OTOH, the hook script *is* a good way to prevent accidental usage.
Regards,
Roel Harbers
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue Feb 1 08:18:58 2005