26
26
``bzr annotate`` display the author instead of the committer.
29
* In addition to global options and command specific options, a set of
30
standard options are now supported. Standard options are legal for
31
all commands. The initial set of standard options are:
33
* ``--help`` or ``-h`` - display help message
34
* ``--verbose`` or ``-v`` - display additional information
35
* ``--quiet`` or ``-q`` - only output warnings and errors.
37
Unlike global options, standard options can be used in aliases and
38
may have command-specific help. (Ian Clatworthy)
40
* Verbosity level processing has now been unified. If ``--verbose``
41
or ``-v`` is specified on the command line multiple times, the
42
verbosity level is made positive the first time then increased.
43
If ``--quiet`` or ``-q`` is specified on the command line
44
multiple times, the verbosity level is made negative the first
45
time then decreased. To get the default verbosity level of zero,
46
either specify none of the above , ``--no-verbose`` or ``--no-quiet``.
47
Note that most commands currently ignore the magnitude of the
48
verbosity level but do respect *quiet vs normal vs verbose* when
49
generating output. (Ian Clatworthy)
29
* In addition to global options and command specific options, a set of
30
standard options are now supported. Standard options are legal for
31
all commands. The initial set of standard options are:
33
* ``--help`` or ``-h`` - display help message
34
* ``--verbose`` or ``-v`` - display additional information
35
* ``--quiet`` or ``-q`` - only output warnings and errors.
37
Unlike global options, standard options can be used in aliases and
38
may have command-specific help. (Ian Clatworthy)
40
* Verbosity level processing has now been unified. If ``--verbose``
41
or ``-v`` is specified on the command line multiple times, the
42
verbosity level is made positive the first time then increased.
43
If ``--quiet`` or ``-q`` is specified on the command line
44
multiple times, the verbosity level is made negative the first
45
time then decreased. To get the default verbosity level of zero,
46
either specify none of the above , ``--no-verbose`` or ``--no-quiet``.
47
Note that most commands currently ignore the magnitude of the
48
verbosity level but do respect *quiet vs normal vs verbose* when
49
generating output. (Ian Clatworthy)
178
181
stack to the log, which can be useful for gathering debug details.
181
* ``bzrlib.pack.ContainerWriter`` now tracks how many records have been
182
added via a public attribute records_written. (Robert Collins)
184
* New method ``bzrlib.transport.Transport.get_recommended_page_size``.
185
This provides a hint to users of transports as to the reasonable
186
minimum data to read. In principle this can take latency and
187
bandwidth into account on a per-connection basis, but for now it
188
just has hard coded values based on the url. (e.g. http:// has a large
189
page size, file:// has a small one.) (Robert Collins)
191
* New method on ``bzrlib.transport.Transport`` ``open_write_stream`` allows
192
incremental addition of data to a file without requiring that all the
193
data be buffered in memory. (Robert Collins)
195
* New methods on ``bzrlib.knit.KnitVersionedFile``:
196
``get_data_stream(versions)``, ``insert_data_stream(stream)`` and
197
``get_format_signature()``. These provide some infrastructure for
198
efficiently streaming the knit data for a set of versions over the smart
201
* Knits with no annotation cache still produce correct annotations.
204
* Three new methods have been added to ``bzrlib.trace``:
205
``set_verbosity_level``, ``get_verbosity_level`` and ``is_verbose``.
206
``set_verbosity_level`` expects a numeric value: negative for quiet,
207
zero for normal, positive for verbose. The size of the number can be
208
used to determine just how quiet or verbose the application should be.
209
The existing ``be_quiet`` and ``is_quiet`` routines have been
210
integrated into this new scheme. (Ian Clatworthy)
212
* Options can now be delcared with a ``custom_callback`` parameter. If
213
set, this routine is called after the option is processed. This feature
214
is now used by the standard options ``verbose`` and ``quiet`` so that
215
setting one implicitly resets the other. (Ian Clatworthy)
217
* Rather than declaring a new option from scratch in order to provide
218
custom help, a centrally registered option can be decorated using the
219
new ``bzrlib.Option.custom_help`` routine. In particular, this routine
220
is useful when declaring better help for the ``verbose`` and ``quiet``
221
standard options as the base definition of these is now more complex
222
than before thanks to their use of a custom callback. (Ian Clatworthy)
184
* ``bzrlib.pack.ContainerWriter`` now tracks how many records have been
185
added via a public attribute records_written. (Robert Collins)
187
* New method ``bzrlib.transport.Transport.get_recommended_page_size``.
188
This provides a hint to users of transports as to the reasonable
189
minimum data to read. In principle this can take latency and
190
bandwidth into account on a per-connection basis, but for now it
191
just has hard coded values based on the url. (e.g. http:// has a large
192
page size, file:// has a small one.) (Robert Collins)
194
* New method on ``bzrlib.transport.Transport`` ``open_write_stream`` allows
195
incremental addition of data to a file without requiring that all the
196
data be buffered in memory. (Robert Collins)
198
* New methods on ``bzrlib.knit.KnitVersionedFile``:
199
``get_data_stream(versions)``, ``insert_data_stream(stream)`` and
200
``get_format_signature()``. These provide some infrastructure for
201
efficiently streaming the knit data for a set of versions over the smart
204
* Knits with no annotation cache still produce correct annotations.
207
* Three new methods have been added to ``bzrlib.trace``:
208
``set_verbosity_level``, ``get_verbosity_level`` and ``is_verbose``.
209
``set_verbosity_level`` expects a numeric value: negative for quiet,
210
zero for normal, positive for verbose. The size of the number can be
211
used to determine just how quiet or verbose the application should be.
212
The existing ``be_quiet`` and ``is_quiet`` routines have been
213
integrated into this new scheme. (Ian Clatworthy)
215
* Options can now be delcared with a ``custom_callback`` parameter. If
216
set, this routine is called after the option is processed. This feature
217
is now used by the standard options ``verbose`` and ``quiet`` so that
218
setting one implicitly resets the other. (Ian Clatworthy)
220
* Rather than declaring a new option from scratch in order to provide
221
custom help, a centrally registered option can be decorated using the
222
new ``bzrlib.Option.custom_help`` routine. In particular, this routine
223
is useful when declaring better help for the ``verbose`` and ``quiet``
224
standard options as the base definition of these is now more complex
225
than before thanks to their use of a custom callback. (Ian Clatworthy)
226
* Use UTF-8 encoded StringIO for log tests to avoid failures on
227
non-ASCII committer names. (Lukáš Lalinský)
231
229
===================