bzr resolve

[Aaron Bentley]

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

On 12-07-26 03:13 PM, Bosco Rama wrote:
> bzr resolve vs bzr resolve *
> 
> Logically the same.  VERY different outcome.

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.

So really, if you treat * as being the same as no-arguments, you're in
for a lot of surprises from all directions.

> My original post simply asked if there was a way to stop the
> resolve command from doing this.  It would appear that the answer
> is 'No'.

That's right.  I did not anticipate that it would be surprising to
have having differing behaviour depending on whether files were
specified.  I'm sorry for the surprise.

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

iEYEARECAAYFAlARp1AACgkQ0F+nu1YWqI1DgwCeKNDHiICuDXmy90SX8J9bDd/e
3wsAnjuNiVWYVdgwLdofmWc6B/tPwUAd
=pYEQ
-----END PGP SIGNATURE-----