bzr pull --verbose should have all formating options that "bzr log" has.

[Matthieu Moy]

bzr pull --verbose is far too verbose for me, I'd like a

$ bzr pull --verbose --line

and indeed, all the formatting options of bzr log would be relevant here (--short, --log-format fmt and maybe --show-id).

[Andrew Bennetts (spiv)]

I'd love to have "bzr pull --verbose --line" as well. I regularly find myself doing this instead:

$ bzr pull
N revisions pulled.
$ bzr log --line -r -N..

[John A Meinel (jameinel)]

We certainly could switch to having '--log-format' as a member for 'pull'. It is pretty trivial. I think we don't really want to have all '--line', '--short', '--long' as part of it.

I'm wondering if an env var would be preferable. Which could set the default log formatter for all commands, which could then be overridden by an explicit request.

[Aaron Bentley (abentley)]

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

John A Meinel wrote:
> We certainly could switch to having '--log-format' as a member for
> 'pull'. It is pretty trivial. I think we don't really want to have all '
> --line', '--short', '--long' as part of it.
>
> I'm wondering if an env var would be preferable. Which could set the
> default log formatter for all commands, which could then be overridden
> by an explicit request.

We already have a log format default, e.g. 'log_format=short'. This
works for most commands, but not 'pull'.

I'm not so sure about providing only --log-format. I eliminated that in
my optparse branch, making log format into an enumeration option. I'd
rather be consistent here, even if it meant doing --short-log,
- --long-log, etc in every command.

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

iD8DBQFExNvd0F+nu1YWqI0RAsvGAJ99ofdB5LkjL9429tzXBl7P+H3+sACfS9TR
x3ZR1WZdW0GPB2M/PIUgwtc=
=AeSm
-----END PGP SIGNATURE-----