| 2009-06-16 08:30:50 |
David I |
bug |
|
|
added bug |
| 2009-06-16 08:45:10 |
Robert Collins |
bzr: status |
New |
Incomplete |
|
| 2009-06-16 11:51:54 |
Vincent Ladeuil |
bzr: importance |
Undecided |
Medium |
|
| 2009-06-16 11:51:54 |
Vincent Ladeuil |
bzr: status |
Incomplete |
Confirmed |
|
| 2009-06-16 11:52:36 |
Vincent Ladeuil |
summary |
STDERR being abused for "trivial" output |
progress report should be user configurable |
|
| 2009-06-17 05:35:59 |
Martin Pool |
summary |
progress report should be user configurable |
don't want progress bars sent to stderr |
|
| 2009-06-19 08:21:34 |
Martin Pool |
branch linked |
|
lp:~mbp/bzr/387717-progress-bar-tty |
|
| 2009-06-19 08:44:17 |
Martin Pool |
bzr: status |
Confirmed |
In Progress |
|
| 2009-06-19 08:44:17 |
Martin Pool |
bzr: assignee |
|
Martin Pool (mbp) |
|
| 2009-06-30 05:17:59 |
Martin Pool |
summary |
don't want progress bars sent to stderr |
only send progress bars to stderr if it's a tty |
|
| 2009-06-30 05:17:59 |
Martin Pool |
description |
I see that some non-error output from bzr commands (e.g. the progress bar during a status with a bzr+ssh parent repos) is being printed to STDERR. On *NIX systems STDERR is not intended for such output. It is an abuse of basic *NIX principles to use STDERR for non-error output. By using it for such "trivia" you risk annoying many UNIX (power-)users. |
If stderr is not a tty, progress bars should not be sent to it. |
|
| 2009-07-23 05:58:36 |
Martin Pool |
bzr: status |
In Progress |
Fix Released |
|
