uncommit output shouldn't go to stderr
Bug #276610 reported by
William Fagan
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
Changed in bzr: | |
status: | New → Confirmed |
tags: | added: uncommit |
tags: | added: check-for-breezy |
To post a comment you must log in.
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.