>> The problem in
>> this case is that svn delete (without --force) didn't work in the first place
>> as opposite action to svn add.
>
>I disagree, and I'll repeat my earlier suggestion, which no-one seems to have picked up on yet:
>
>"svn delete" shouldn't be trying to be the opposite of "svn add", it should by trying to be the same as a normal "rm" (or "del"), plus updating the Subversion data as necessary to record what it has done. "svn delete" should *always* delete the file in the working copy, and there should be no doubt in anyone's mind that it is going to do so since a "golden rule" should be that "svn XYZ" does the same as the OS XYZ command plus updating the Subversion data.
>
>Reversing an add is not the same as deleting a file; it could perhaps be "svn subtract", "svn release", or something.
I understand your proposal. But my understanding of add and remove is
a bit different. svn delete is quite the only command that even has a shell
partner, there's no add, commit, update and stuff on the shell, so I don't
see that as a strong argument. svn add just adds an already existing file
_to version control_. It doesn't create a new file. For the same reason svn
delete should just delete the file _from version control_, without touching
the file itself. But as svn delete already exists now we might go your way
and introduce a new command to do this action. But anyway I'm only a
user, not a developer, so I'll leave the decision to others.
bye Fabi
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Apr 19 14:08:26 2006