10
This release adds a translation of some of the user documentation into Spanish.
11
(Contributions of other translations would be very welcome.)
13
* Avoid KnitCorrupt error extracting inventories from some repositories.
14
(The data is not corrupt; an internal check is detecting a problem
15
reading from the repository.)
16
(Martin Pool, Andrew Bennetts, Robert Collins, #234748)
18
* Inserting a bundle which changes the contents of a file with no trailing
19
end of line, causing a knit snapshot in a 'knits' repository will no longer
20
cause KnitCorrupt. (Robert Collins)
22
* Sanitize branch nick before using it as an attachment filename in
23
``bzr send``. (Lukáš Lalinský, #210218)
27
* Added the 'alias' command to set/unset and display aliases. (Tim Penhey)
29
* ``added``, ``modified``, and ``unknowns`` behaviour made consistent (all three
30
now quote paths where required). Added ``--null`` option to ``added`` and
31
``modified`` (for null-separated unknowns, use ``ls --unknown --null``)
36
* ``bzr status`` was breaking if you merged the same revision twice.
37
(John Arbash Meinel, #235407)
41
* Added *Bazaar Zen* section to the User Guide. (Ian Clatworthy)
45
* Fix the test HTTPServer to be isolated from chdir calls made while it is
46
running, allowing it to be used in blackbox tests. (Robert Collins)
50
* ``WorkingTree.set_parent_(ids/trees)`` will now filter out revisions
51
which are in the ancestry of other revisions. So if you merge the same
52
tree twice, or merge an ancestor of an existing merge, it will only
53
record the newest. (If you merge a descendent, it will replace its
54
ancestor). (John Arbash Meinel, #235407)
58
* Knit record serialisation is now stricter on what it will accept, to
59
guard against potential internal bugs, or broken input. (Robert Collins)
62
bzr 1.6beta1 2008-06-02
63
-----------------------
66
Commands that work on the revision history such as push, pull, missing,
67
uncommit and log are now substantially faster. This release adds a
68
translation of some of the user documentation into Spanish. (Contributions of
69
other translations would be very welcome.) Bazaar 1.6beta1 adds a new network
70
protocol which is used by default and which allows for more efficient transfers
71
and future extensions.
13
74
NOTES WHEN UPGRADING:
19
* Adding ``-Derror`` will now display a traceback when a plugin fails to
22
76
* There is a new version of the network protocol used for bzr://, bzr+ssh://
23
77
and bzr+http:// connections. This will allow more efficient requests and
24
78
responses, and more graceful fallback when a server is too old to
28
82
these protocols. Use alternatives like SFTP or upgrade those servers.
29
83
(Andrew Bennetts, #83935)
87
* Deprecation warnings will not be suppressed when running ``bzr selftest``
88
so that developers can see if their code is using deprecated functions.
93
* Adding ``-Derror`` will now display a traceback when a plugin fails to
98
* ``bzr branch/push/pull -r XXX`` now have a helper function for finding
99
the revno of the new revision (``Graph.find_distance_to_null``). This
100
should make something like ``bzr branch -r -100`` in a shared, no-trees
101
repository much snappier. (John Arbash Meinel)
103
* ``bzr log --short -r X..Y`` no longer needs to access the full revision
104
history. This makes it noticeably faster when logging the last few
105
revisions. (John Arbash Meinel)
33
107
* ``bzr ls`` now accepts ``-V`` as an alias for ``--versioned``.
34
108
(Jerad Cramp, #165086)
37
111
``Graph.find_differences`` to determine missing revisions without having
38
112
to search the whole ancestry. (John Arbash Meinel, #174625)
114
* ``bzr uncommit`` now uses partial history access, rather than always
115
extracting the full revision history for a branch. This makes it
116
resolve the appropriate revisions much faster (in testing it drops
117
uncommit from 1.5s => 0.4s). It also means ``bzr log --short`` is one
118
step closer to not using full revision history.
119
(John Arbash Meinel, #172649)
123
* ``bzr merge --lca`` should handle when two revisions have no common
124
ancestor other than NULL_REVISION. (John Arbash Meinel, #235715)
126
* ``bzr status`` was breaking if you merged the same revision twice.
127
(John Arbash Meinel, #235407)
42
129
* ``bzr push`` with both ``--overwrite`` and ``-r NNN`` options no longer
43
130
fails. (Andrew Bennetts, #234229)
90
180
on the plugin and integration chapters of the User Guide.
183
* More Bazaar developer documentation about packaging and release process,
184
and about use of Python reprs.
185
(Martin Pool, Martin Albisetti)
93
187
* Updated Tortise strategy document. (Mark Hammond)
191
* ``bzrlib.tests.adapt_tests`` was broken and unused - it has been fixed.
194
* Fix the test HTTPServer to be isolated from chdir calls made while it is
195
running, allowing it to be used in blackbox tests. (Robert Collins)
97
197
* New helper function for splitting test suites
98
198
``split_suite_by_condition``. (Robert Collins)
202
* ``Branch.missing_revisions`` has been deprecated. Similar functionality
203
can be obtained using ``bzrlib.missing.find_unmerged``. The api was
204
fairly broken, and the function was unused, so we are getting rid of it.
104
209
* ``Branch.abspath`` is deprecated; use the Tree or Transport
105
210
instead. (Martin Pool)
212
* ``Branch.update_revisions`` now takes an optional ``Graph``
213
object. This can be used by ``update_revisions`` when it is
214
checking ancestry, and allows callers to prefer request to go to a
215
local branch. (John Arbash Meinel)
107
217
* Branch, Repository, Tree and BzrDir should expose a Transport as an
108
218
attribute if they have one, rather than having it indirectly accessible
109
219
as ``.control_files._transport``. This doesn't add a requirement
125
235
``bzrlib.revision`` deprecated before bzrlib 1.5 have been removed.
238
* ``RevisionSpec.wants_revision_history`` can be set to False for a given
239
``RevisionSpec``. This will disable the existing behavior of passing in
240
the full revision history to ``self._match_on``. Useful for specs that
241
don't actually need access to the full history. (John Arbash Meinel)
128
243
* The constructors of ``SmartClientMedium`` and its subclasses now require a
129
244
``base`` parameter. ``SmartClientMedium`` implementations now also need
130
245
to provide a ``remote_path_from_transport`` method. (Andrew Bennetts)
142
257
insert_record_stream are meant to efficiently replace this method.
260
* ``WorkingTree.set_parent_(ids/trees)`` will now filter out revisions
261
which are in the ancestry of other revisions. So if you merge the same
262
tree twice, or merge an ancestor of an existing merge, it will only
263
record the newest. (If you merge a descendent, it will replace its
264
ancestor). (John Arbash Meinel, #235407)
145
266
* ``WorkingTreeFormat2.stub_initialize_remote`` is now private.
added
removed
NEWS
