RFC: Add option --quiet=LEVEL to disable output
Lars Wirzenius
liw at liw.iki.fi
Sun Jan 28 12:46:42 GMT 2007
On su, 2007-01-28 at 14:36 +0200, Jari Aalto wrote:
> To make bzr work from scripts, the current verbosiness is geares towards
> interactive user. Let's say:
>
> 1. Download tarball
> 2. Unpack
> 3. put it in bzr (bzr init)a
> 4. Add file (bzr add)
> 5. Put automatic commit message, derived form version (bzr ci)
>
> All those operations the script can do by itself. If the commands (or
> bzr itself) would have:
>
> --quiet
The bzr.dev branch seems to have:
liw at gytha$ ~/bzr.dev/bzr.dev/bzr help global-options
Global Options
These options may be used with any command, and may appear in front of
any
command. (e.g. "bzr --quiet help").
--quiet Suppress informational output; only print errors and
warnings
--version Print the version number
--no-aliases Do not process command aliases when running this command
--builtin Use the built-in version of a command, not the plugin
version.
This does not suppress other plugin effects
--no-plugins Do not process any plugins
--Derror Instead of normal error handling, always print a
traceback on
error.
--profile Profile execution using the hotshot profiler
--lsprof Profile execution using the lsprof profiler
--lsprof-file Profile execution using the lsprof profiler, and write
the
results to a specified file.
Note: --version must be supplied before any command.
liw at gytha$
Personally, I think it would be good to list those global options that
are not related to development of bzr itself in the option listing for
each command. Better discoverability.
--
Comedy evolution: survival of the wittiest
More information about the bazaar
mailing list