default scope of different bzr commands

[Russ Brown]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Kuno Meyer wrote:
> 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.
> 

I actually get quite annoyed by this when using bzr status while I'm in
a subdirectory. I'll often want to copy and paste a number of filenames
from the output to add, rm, ci or whatever, and am frustrated to find
that it doesn't work because the paths shown are relative to the branch
root, and not to where I am.

Back when I was evaluating git (before deciding on bzr), it worked in
the same way and I brought it up on the mailing list. My comments were
pretty much shot down, but oddly enough a while later it happened, and
now the output from git status is relative to the CWD.

I'd like to see this in bazaar, even as an option to status that I can
alias.

- --

Russ.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFJE20ahXYlbEtYt2wRAqbVAKCNRBv4+mZ1pH0MLEcrv5hDPuM5xQCdGHFL
4i8jvAJcBn3eGr5nEihANiI=
=+Jck
-----END PGP SIGNATURE-----