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

Should revert be non-destructive by default?

From: <peter_at_pdavis.cx>
Date: 2003-01-21 13:00:30 CET

Hash: SHA1

On Tuesday 21 January 2003 03:02, Rafael Garcia-Suarez wrote:
 I've already done this to revert a prop change :
     $ svn revert my_project_root_dir
 I'd be pretty annoyed if this caused the loss of all my local changes...

True, true. I thought of that as soon as I said I can't think of any use
cases. Directory properties and destructive reverts give a pretty good
reason why non-recursive should be default.

That still leaves a couple ideas for improvement.

* Have a separate command to revert adds and deletes (and renames), and
  ensure that this new command is non-destructive except for add/delete.
  This has been discussed before. The new command could be recursive by
* Alternatively, make revert non-destructive. This would allow it to be
  recursive by default, since there would be no danger of accidentally
  overwriting local mods.
  * Require --force only when run recursively on directories in order to
    overwrite local mods (other than add/delete),

  * Or always require --force. Somehow this seems attractive to me.

Is revert the only current svn command, other than prop*, that will
obliterate local mods without --force?

- --
Peter Davis
Version: GnuPG v1.2.1 (GNU/Linux)


To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sat Oct 14 02:03:40 2006

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.