> From: Philip Martin [mailto:pm@localhost]On Behalf Of Philip Martin
> Sent: 22 April 2002 14:20
[...]
> Here's how I would like 'svn rm' to work: after 'svn rm' the files are
> always removed.
++1
> However 'svn rm' first checks for modifications and if
> there are any the command fails. When 'svn rm' fails either the
> --force flag can be used or 'svn revert' can be used first to remove
> the modifications. This applies both to files and file properties,
> and also to directories, in which case the children of the directory
> are checked as well.
/me nods
> This scheme also solve the problem that after an 'svn rm' on a
> modified file, which at present is allowed, there is no simple way to
> undo the deletion and retain the modification. I think it would be
> better for the user to either choose to revert the modification before
> the 'svn rm' succeeds, or to have to --force the 'svn rm'.
Yes, this would prevent the user from modifying a deleted file.
> I would really like 'svn rm directory' to remove the directory from
> the filesystem, as well as removing any files it contains. Perhaps we
> could move it into the .svn area?
If you mean the .svn area of the removed directories parent dir: +1.
This will probably make it harder to implement, but I think that is
worth the trouble (but hey, I'm not working on that area, so that's
not worth much). Once the deletion of the dir is committed it can
be removed from the .svn area again.
Sander
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Mon Apr 22 14:32:08 2002