[bug] commands output inconsistence
Aaron Bentley
aaron.bentley at utoronto.ca
Wed Jul 26 14:39:20 BST 2006
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Alexander Belchenko wrote:
> If I understand correctly there is several types of bzr output:
>
> - errors and warnings messages
> - progress bar (each command could potentially has progress bar)
> - informational output
No, it's more like:
- - errors and warnings
- - progress
- - primary output
- - secondary output
The purpose of some commands is to produce output. Examples: 'bzr ls',
'bzr status'. They can produce primary output, and they can produce
secondary output.
The purpose of other commands is to perform an action. Examples: 'bzr
commit', 'bzr merge'. These commands should only produce secondary output.
Only primary output is sent to stdout. All other output is sent to stderr.
> I simply wanted to have ability easy redirect output of commands to
> file. It could be useful for creating examples for documentation or for
> preparing bug reports.
There ought to be an easy way to redirect stderr on Windows. There
certainly is on *nix.
Aaron
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
iD8DBQFEx3CI0F+nu1YWqI0RAnYaAJ4twL9NLn9z4kg/QCI6Vl1DhgMI+QCcDcW0
HKnEM1c0IMZbPhs6Mhmn0dA=
=cq8p
-----END PGP SIGNATURE-----
More information about the bazaar
mailing list