RFC: bzr rm is hard to use

[Robert Collins]

So, we've got a very complex 'bzr rm'. I don't know about you guys, but
I'm starting to hate using it - I *always* end up having to type
'--force' because we're hugely cautious.

Now, this may be polish, or deeper, but I'd like to fix it.

Specifically, I'd like (and some of these may be current behaviour):
'bzr rm' of an added file to do what 'bzr revert' of the same file does:
- just unversion it. *IF* --force' is given then delete it.
'bzr rm' of a missing file to Just Do It
'bzr rm' of a file that has been modified by me to mv it to a backup
using the same scheme 'bzr revert' does.
'bzr rm' of an unmodified file to Just Do It
'bzr rm --keep' on any of the cases above that remove the file to
preserve the file on disk.

-Rob
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 197 bytes
Desc: This is a digitally signed message part
Url : https://lists.ubuntu.com/archives/bazaar/attachments/20090716/f47933ae/attachment.pgp