bzr resolve

[John Yates]

Aaron Bentley <aaron at aaronbentley.com> writes:

> Thanks for explaining your rationale.  There are a number of
> counter-examples to the idea that these are logically the same.
> 
> Standard *nix commands that accept multiple filenames: cat, chmod,
> chown, gzip/gunzip, grep, "ls -a", rm, wc
> 
> bzr commands that accept multiple filenames: add, ignore, log, remove,
> resolve, revert.
> 
> As well as these differences, * differs from Bazaar's default
> behaviour because it does not select the whole tree.  Unlike Bazaar,
> it is does not descend into subdirectories, and if a filename begins
> with ".", it is ignored.  Also, * is not expanded if there are no
> files in the directory, so "ls *" in an empty directory is an error,
> but "ls" is not.

Resolve's behavior in the presence of an argument is the sort of atypical 
behavior that in most UX experts would suggest requires some form of 
confirmation or override (e.g. --force).  While you do indeed give *nix 
example in which commands' behaviors change none exhibit a change from 
safe to unsafe merely for adding an argument.

/john