uncommit output shouldn't go to stderr

Bug #276610 reported by William Fagan
2
Affects Status Importance Assigned to Milestone
Bazaar
Confirmed
Undecided
Unassigned

Bug Description

There is 2 parts of the uncommit output that go to stderr which I think should go to stdout.

Are you sure [y/N]?

You can restore the old tip by running:
  bzr pull . -r revid:<email address hidden>

I'm running 1.7

Revision history for this message
William Fagan (libwilliam-deactivatedaccount) wrote :

Also update has some output going to stderr which I don't think should be.

First one is questionable (when a tree is up to date already). Technically nothing went wrong so I don't know if it should go to stderr or not.
     Tree is up to date at revision 9.

The second one I am pretty sure should not go to stderr (on a successful update).
     All changes applied successfully.
     Updated to revision 10.

Revision history for this message
William Fagan (libwilliam-deactivatedaccount) wrote :

Commit does the same... This goes to stderr.

Committing to: /home/will/test/
Committed revision 14.

It seems like a lot of them are going to stderr so maybe this was a design choice. Not sure.

Revision history for this message
Robert Collins (lifeless) wrote : Re: [Bug 276610] Re: uncommit output shouldn't go to stderr

On Wed, 2008-10-01 at 07:37 +0000, William Fagan wrote:
>
> It seems like a lot of them are going to stderr so maybe this was a
> design choice. Not sure.

Indeed, its a design choice; I believe we document it in HACKING.

Basically we want:
 - the core output of a command to stdout
 - everything else to stderr

(so bzr -q command / -v command won't usually change the std output at
all, they will however add/remove output on stderr)

-Rob

--
GPG key available at: <http://www.robertcollins.net/keys.txt>.

Revision history for this message
William Fagan (libwilliam-deactivatedaccount) wrote :

Alright, thanks for commenting Rob.

On Wed, Oct 1, 2008 at 1:53 PM, Robert Collins <email address hidden>wrote:

> On Wed, 2008-10-01 at 07:37 +0000, William Fagan wrote:
> >
> > It seems like a lot of them are going to stderr so maybe this was a
> > design choice. Not sure.
>
> Indeed, its a design choice; I believe we document it in HACKING.
>
> Basically we want:
> - the core output of a command to stdout
> - everything else to stderr
>
> (so bzr -q command / -v command won't usually change the std output at
> all, they will however add/remove output on stderr)
>
> -Rob
>
> --
> GPG key available at: <http://www.robertcollins.net/keys.txt>.
>
> --
> uncommit output shouldn't go to stderr
> https://bugs.launchpad.net/bugs/276610
> You received this bug notification because you are a direct subscriber
> of the bug.
>

Changed in bzr:
status: New → Confirmed
Jelmer Vernooij (jelmer)
tags: added: uncommit
Jelmer Vernooij (jelmer)
tags: added: check-for-breezy
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.