15
This release of Bazaar contains many improvements to the speed,
16
documentation and functionality of ``bzr log`` and the display of logged
17
revisions by ``bzr status``. bzr now also gives a better indication of
18
progress, both in the way operations are drawn onto a text terminal, and
19
by showing the rate of network IO.
21
Changes from RC1 to Final
22
*************************
24
* ``bzr init --development-wt5[-rich-root]`` would fail because of
25
circular import errors. (John Arbash Meinel, #328135)
27
* Expanded the help for log and added a new help topic called
28
``log-formats``. (Ian Clatworthy)
33
* By default, ``bzr status`` after a merge now shows just the pending
34
merge tip revisions. This improves the signal-to-noise ratio after
35
merging from trunk and completes much faster. To see all merged
36
revisions, use the new ``-v`` flag. (Ian Clatworthy)
38
* ``bzr log --line`` now shows any tags after the date and before
39
the commit message. If you have scripts which parse the output
40
from this command, you may need to adjust them accordingly.
43
* ``bzr log --short`` now shows any additional revision properties
44
after the date and before the commit message. Scripts that parse
45
output of the log command in this situation may need to adjust.
46
(Neil Martinsen-Burrell)
48
* The experimental formats ``1.12-preview`` and ``1.12-preview-rich-root``
49
have been renamed ``development-wt5`` and ``development-wt5-rich-root``
50
respectively, given they are not ready for release in 1.12.
53
* ``read_bundle_from_url`` has been deprecated. (Vincent Ladeuil)
58
* Add support for filtering ``bzr missing`` on revisions. Remote revisions
59
can be filtered using ``bzr missing -r -20..-10`` and local revisions can
60
be filtered using ``bzr missing --my-revision -20..-10``.
63
* ``bzr log -p`` displays the patch diff for each revision.
64
When logging a file, the diff only includes changes to that file.
65
(Ian Clatworthy, #202331, #227335)
67
* ``bzr log`` supports a new option called ``-n N`` or ``--level N``.
68
A value of 0 (zero) means "show all nested merge revisions" while
69
a value of 1 (one) means "show just the top level". Values above
70
1 can be used to see a limited amount of nesting. That can be
71
useful for seeing the level or two below PQM submits for example.
72
To force the ``--short`` and ``--line`` formats to display all nested
73
merge revisions just like ``--long`` does by default, use a command
74
like ``bzr log --short -n0``. To display just the mainline using
75
``--long`` format, ``bzr log --long -n1``.
81
* ``bzr add`` more clearly communicates success vs failure.
84
* ``bzr init`` will now print a little less verbose output.
87
* ``bzr log`` is now much faster in many use cases, particularly
88
at incrementally displaying results and filtering by a
89
revision range. (Ian Clatworthy)
91
* ``bzr log --short`` and ``bzr log --line`` now show tags, if any,
92
for each revision. The tags are shown comma-separated inside
93
``{}``. For short format, the tags appear at the end of line
94
before the optional ``[merge]`` indicator. For line format,
95
the tags appear after the date. (Ian Clatworthy)
97
* Progress bars now show the rate of activity for some SFTP
98
operations, and they are drawn different. (Martin Pool, #172741)
100
* Progress bars now show the rate of activity for urllib and pycurl based
101
HTTP client implementations. The operations are tracked at the socket
102
level for better precision.
105
* Rule-based preferences can now accept multiple patterns for a set of
106
rules. (Marius Kruger)
108
* The ``ancestor:`` revision spec will now default to referring to the
109
parent of the branch if no other location is given.
110
(Daniel Watkins, #198417)
112
* The debugger started as a result of setting ``$BZR_PDB`` works
113
around a bug in ``pdb``, http://bugs.python.org/issue4150. The bug
114
can cause truncated tracebacks in Python versions before 2.6.
117
* VirtualVersionedFiles now implements
118
``iter_lines_added_or_present_in_keys``. This allows the creation of
119
new branches based on stacked bzr-svn branches. (#311997)
124
* ``bzr annotate --show-ids`` doesn't give a backtrace on empty files
126
(Anne Mohsen, Vincent Ladeuil, #314525)
128
* ``bzr log FILE`` now correctly shows mainline revisions merging
129
a change to FILE when the ``--short`` and ``--line`` log formats
130
are used. (Ian Clatworthy, #317417)
132
* ``bzr log -rX..Y FILE`` now shows the history of FILE provided
133
it existed in Y or X, even if the file has since been deleted or
134
renamed. If no range is given, the current/basis tree and
135
initial tree are searched in that order. More generally, log
136
now interprets filenames in their historical context.
137
(Ian Clatworthy, #175520)
139
* ``bzr status`` now reports nonexistent files and continues, then
140
errors (with code 3) at the end. (Karl Fogel, #306394)
142
* Don't require the present compression base in knits to be the same
143
when adding records in knits. (Jelmer Vernooij, #307394)
145
* Fix a problem with CIFS client/server lag on Windows colliding with
146
an invariant-per-process algorithm for generating AtomicFile names
147
(Adrian Wilkins, #304023)
149
* Many socket operations now handle EINTR by retrying the operation.
150
Previously EINTR was treated as an unrecoverable failure. There is
151
a new ``until_no_eintr`` helper function in ``bzrlib.osutils``.
154
* Support symlinks with non-ascii characters in the symlink filename.
155
(Jelmer Vernooij, #319323)
157
* There was a bug in how we handled resolving when a file is deleted
158
in one branch, and modified in the other. If there was a criss-cross
159
merge, we would cause the deletion to conflict a second time.
160
(Vincent Ladeuil, John Arbash Meinel)
162
* There was another bug in how we chose the correct intermediate LCA in
163
criss-cross merges leading to several kind of changes be incorrectly
165
(John Arbash Meinel, Vincent Ladeuil)
167
* Unshelve now handles deleted paths without crashing. (Robert Collins)
172
* Improved plugin developer documentation. (Martin Pool)
177
* ``ProgressBarStack`` is deprecated; instead use
178
``ui_factory.nested_progress_bar`` to create new progress bars.
181
* ForeignVcsMapping() now requires a ForeignVcs object as first
182
argument. (Jelmer Vernooij)
184
* ForeignVcsMapping.show_foreign_revid() has been moved to
185
ForeignVcs. (Jelmer Vernooij)
187
* ``read_bundle_from_url`` is deprecated in favor of
188
``read_mergeable_from_url``. (Vincent Ladeuil)
190
* Revision specifiers are now registered in
191
``bzrlib.revisionspec.revspec_registry``, and the old list of
192
revisionspec classes (``bzrlib.revisionspec.SPEC_TYPES``) has been
193
deprecated. (Jelmer Vernooij, #321183)
195
* The progress and UI classes have changed; the main APIs remain the
196
same but code that provides a new UI or progress bar class may
197
need to be updated. (Martin Pool)
202
* Default User Interface (UI) is CLIUIFactory when bzr runs in a dumb
203
terminal. It is sometimes desirable do override this default by forcing
204
bzr to use TextUIFactory. This can be achieved by setting the
205
BZR_USE_TEXT_UI environment variable (emacs shells, as opposed to
206
compile buffers, are such an example).
209
* New API ``Branch.iter_merge_sorted_revisions()`` that iterates over
210
``(revision_id, depth, revno, end_of_merge)`` tuples.
213
* New ``Branch.dotted_revno_to_revision_id()`` and
214
``Branch.revision_id_to_dotted_revno()`` APIs that pick the most
215
efficient way of doing the mapping.
218
* Refactor cmd_serve so that it's a little easier to build commands that
219
extend it, and perhaps even a bit easier to read. (Jonathan Lange)
221
* ``TreeDelta.show()`` now accepts a ``filter`` parameter allowing log
222
formatters to retrict the output.
227
vim: tw=74 ft=rst ff=unix
added
removed
doc/en/release-notes/bzr-1.12.txt
