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 weaves than knits. 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.
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
added
removed
NEWS
