[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: Steve Williams <stevewilliams_at_kromestudios.com>
Date: 2005-11-04 00:30:52 CET

Michael Sweet wrote:
>>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.

The 'purge' as described in the original post removes all unversioned
files from a WC. You're probably thinking of the 'obliterate' command
that has been proposed here before.

This message and its attachments may contain legally privileged or confidential information. This message is intended for the use of the individual or entity to which it is addressed. If you are not the addressee indicated in this message, or the employee or agent responsible for delivering the message to the intended recipient, you may not copy or deliver this message or its attachments to anyone. Rather, you should permanently delete this message and its attachments and kindly notify the sender by reply e-mail. Any content of this message and its attachments, which does not relate to the official business of the sending company must be taken not to have been sent or endorsed by the sending company or any of its related entities. No warranty is made that the e-mail or attachment(s) are free from computer virus or other defect.
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:31:46 2005

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

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.