5
Release 0.8 of bzr introduces a new format for history storage, called
6
'knit', as an evolution of to the 'weave' format used in 0.7. Local
7
and remote operations are faster using knits than weaves. Several
8
operations including 'init', 'init-repo', and 'upgrade' take a
9
--format option that controls this. Branching from an existing branch
10
will keep the same format.
12
It is possible to merge, pull and push between branches of different
13
formats but this is slower than moving data between homogenous
14
branches. It is therefore recommended (but not required) that you
15
upgrade all branches for a project at the same time. Information on
16
formats is shown by 'bzr info'.
18
bzr 0.8 now allows creation of 'repositories', which hold the history
19
of files and revisions for several branches. Previously bzr kept all
20
the history for a branch within the .bzr directory at the root of the
21
branch, and this is still the default. To create a repository, use
22
the new 'bzr init-repo' command. Branches exist as directories under
23
the repository and contain just a small amount of information
24
indicating the current revision of the branch.
26
bzr 0.8 also supports 'checkouts', which are similar to in cvs and
27
subversion. Checkouts are associated with a branch (optionally in a
28
repository), which contains all the historical information. The
29
result is that a checkout can be deleted without losing any
30
already-committed revisions. A new 'update' command is also available.
32
Repositories and checkouts are not supported with the 0.7 storage
33
format. To use them you must upgrad to either knits, or to the
34
'metaweave' format, which uses weaves but changes the .bzr directory
100
135
* Hitting CTRL-C while doing an SFTP push will no longer cause stale locks
101
136
to be left in the SFTP repository. (Robert Collins, Martin Pool).
138
* New option 'diff --prefix' to control how files are named in diff
139
output, with shortcuts '-p0' and '-p1' corresponding to the options for
140
GNU patch. (Alexander Belchenko, Goffredo Baroncelli, Martin Pool)
142
* Add --revision option to 'annotate' command. (Olaf Conradi)
144
* Add --revision option to 'annotate' command. (Olaf Conradi)
146
* If bzr shows an unexpected revision-history after pulling (perhaps due
147
to a reweave) it can now be corrected by 'bzr reconcile'.
105
152
* Commit is now verbose by default, and shows changed filenames and the
112
159
* Make 'pull' and 'push' remember location on failure using --remember.
162
* For compatibility, make old format for using weaves inside metadir
163
available as 'metaweave' format. Rename format 'metadir' to 'default'.
164
Clean up help for option --format in commands 'init', 'init-repo' and
165
'upgrade'. (Olaf Conradi)
117
169
* The internal storage of history, and logical branch identity have now
159
211
* Deprecated BzrError AmbiguousBase. (Olaf Conradi)
213
* WorkingTree.branch is now a read only property. (Robert Collins)
215
* bzrlib.ui.text.TextUIFactory now accepts a bar_type parameter which
216
can be None or a factory that will create a progress bar. This is
217
useful for testing or for overriding the bzrlib.progress heuristic.
161
220
* New API method get_physical_lock_status() to query locks present on a
162
221
transport. (Olaf Conradi)
223
* Repository.reconcile now takes a thorough keyword parameter to allow
224
requesting an indepth reconciliation, rather than just a data-loss
225
check. (Robert Collins)
227
* bzrlib.ui.ui_factory protocol now supports 'get_boolean' to prompt
228
the user for yes/no style input. (Robert Collins)
166
232
* SFTP tests now shortcut the SSH negotiation, reducing test overhead
added
removed
NEWS
