bzr rm silently does nothing in the root of a working tree

[Mark Hammond]

If you execute 'bzr rm dir', where dir points at the root of a working tree, bzr silently takes no action. This is true even when dir is specified as '.'

bzr should probably just report that it ignored the command - an error might be best from an API point of view so that callers can detect the situation, but that is for others to decide.

[Robert Collins (lifeless)]

Definitely a bug; it should probably behave like 'bzr rm', much as 'bzr
add' behaves like 'bzr add ROOT'.

--
GPG key available at: <http://www.robertcollins.net/keys.txt>.

[Alexander Belchenko (bialix)]

This is more confusing when you invoke rm on a nested branch. I think bzr should print error message.

C:\Temp>cd 1
C:\Temp\1>

C:\Temp\1>bzr init a
Created a standalone tree (format: pack-0.92)

C:\Temp\1>bzr init .
Created a standalone tree (format: pack-0.92)

C:\Temp\1>bzr st
unknown:
  a/

C:\Temp\1>bzr ignore ./a

C:\Temp\1>bzr st
added:
  .bzrignore

C:\Temp\1>bzr rm a

C:\Temp\1>bzr rm not-existent
not-existent does not exist.

C:\Temp\1>mkdir foo

C:\Temp\1>bzr st
added:
  .bzrignore
unknown:
  foo/

C:\Temp\1>bzr rm foo
bzr: ERROR: Can't safely remove modified or unknown files:
unknown:
  foo/
Use --keep to not delete them, or --force to delete them regardless.

C:\Temp\1>bzr ignore foo

C:\Temp\1>bzr st
added:
  .bzrignore

C:\Temp\1>bzr rm foo
deleted foo