[bug] commands output inconsistence
Erik Bågfors
zindar at gmail.com
Wed Jul 26 11:51:48 BST 2006
I disagree.
Output that you might want to filter/capture etc should go to stdout,
other things to stderr. So
bzr status -> stdout
bzr ci -m foo... has nothing you would want to filter, -> stderr.
statusbar -> stderr
On 7/26/06, Alexander Belchenko <bialix at ukr.net> wrote:
> If redirect output of different commands to a file via '>' then I could
> see that some commands print their output to stderr not to stdout.
>
> Let's see:
>
> $ bzr mkdir dir > out ===> output normally redirected to out
I think this should go to stderr.
> $ bzr st > out ===> output normally redirected to out
good
> $ bzr ci -m initial > out ===> out file is empty and output prints on
> the screen:
> added dir
> Committed revision 1.
good
> $ bzr branch a b > out ===> out file is empty and output prints on the
> screen:
> Branched 1 revision(s).
good
> $ bzr merge ../b > out ===> out file is empty and output prints on the
> screen:
> All changes applied successfully.
good
> I think this bug appears because of progress bar. But anyway it's a bug
> for me.
Not for me.
/Erik
--
google talk/jabber. zindar at gmail.com
SIP-phones: sip:erik_bagfors at gizmoproject.com
sip:17476714687 at proxy01.sipphone.com
More information about the bazaar
mailing list