default scope of different bzr commands

[Kuno Meyer]

Hi all

Is there a specific reason, why the default scope of the "bzr add" 
command is "." (e.g. "bzr add" is equivalent to "bzr add ."), whereas 
for most of the other working tree related commands (like "bzr st", "bzr 
diff", "bzr ignore", "bzr revert", ...), it is the branch root? Even 
"bzr ignored" operates on the whole branch, whereas "bzr ls" assumes ".".

This inconsistency is quite confusing to me, leading to occasional usage 
errors of the type of "more/less work done than expected". I'd prefer to 
have an identical default scope for all commands, possibly the branch root.

In addition, I wanted to mention that I was quite surprised today to see 
  that "bzr add" seemingly ignores .bzrignore:

	mkdir a; touch a\b
	bzr init; bzr ignore a
	cd a
	bzr add

(... well, the behaviour can be seen as correct according to the 
documentation, but nevertheless ...)

Cheers
Kuno