Comment 0 for bug 252834

RLVJ (nathan-johnson) wrote :

Since --quiet is likely to be used in serving, it must in some scenarios be absolutely silent.
It may have it's stdout and sterr file descriptors closed before being exec()ed.
If bzr tries to output in that case, it will be killed.

If bzr serve runs in a separate process, it should close it's own stdout and stderr; in any case, it should completely avoid output when called with --quiet.

Strict silence might not be as important for other commands (branch, pull, ...).

Perhaps quiet or another option should be a command, which after being executed will silence the bzr instance for all commands until verbosity is reactivated.