[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: [RFC] 'basic/additional command set' - adding svn subcommands without destroying our learning curve

From: Michael Sweet <mike_at_easysw.com>
Date: 2005-11-04 00:19:27 CET

Branko Čibej wrote:
> ...
>>> svn util purge
>> Slightly off-topic, but when you do implement a "purge" command,
>> would it make more sense to be part of svnadmin since there is no
>> way to "undo" the purge?
> Svnadmin is for repository management. The proposed "purge" command is
> for working copy management, so it doesn't belong in svnadmin.

As I understand it, "purge" would remove all revisions of a file from
the repository, possibly leaving the WC file alone. I would argue
that removing a file and its history from a repo without the
possibility of recovery falls under repository management, not WC
management. A WC operation can be "undone" by reverting a change,
a repo operation can't.

I know I will want to limit access to "purge" to administrative
users only, since I don't want to get a call asking if I can
restore all of the files a user purged "by accident". Sure, I'll
have backups of the repo itself, but I'd rather make it harder
rather than easier to purge files from a repo. Putting the purge
command in svnadmin would immediately "hide" the command from users
that only know to use svn, and it would also make it clear that
"purge" is a serious operation that should only be done by someone
that is managing the repository.

Michael Sweet, Easy Software Products           mike at easysw dot com
Internet Printing and Publishing Software        http://www.easysw.com
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Fri Nov 4 00:21:53 2005

This is an archived mail posted to the Subversion Dev mailing list.