16
16
2.1, 2.2, 2.3 and 2.4, and can read and write repositories generated by all
19
Overriding configuration options from the command line
20
******************************************************
22
The ``-O`` parameter available for all bzr commands allows a user to
23
override a configuration option from the command line. For example::
25
bzr pull -v -Olog_format=line
27
will change the way the pulled revisions are displayed (the default log
28
format is ``long``). This a work in progress and only some options are
31
Working on a posix system without a locale
32
******************************************
34
Previously bzr needed a valid locale set to work with branches containing
35
non-ascii filenames. It will now use utf-8 rather than ascii as a fallback
36
encoding for interacting with the filesystem. This makes creating a working
37
tree and commiting to it possible for such branches in most environments.
42
A large number of new methods have been added to the smart server, making
43
raw file access through the VFS unnecessary in almost all situations, with
44
the major exception of operations involving stacked branches.
46
Commands that have become significantly faster when using a remote branch
47
over ``bzr://``, ``bzr+ssh://`` or ``bzr+http://`` include:
49
* ``bzr checkout --lightweight``
55
Several commands which used to make multiple connections to the server now
56
make only a single one. Connection setup has a fairly high overhead,
57
especially to Launchpad, so this can save several seconds for some
60
To benefit from the improved smart server, both the server and the
61
client need to be running bzr 2.5.
63
Basic colocated branch support
64
******************************
66
The UI now has basic support for colocated branches. In full URLs,
67
a specific colocated branch can be specified using URL path segment
68
parameters. For example a branch named ``stronk`` could be addressed using
69
``http://example.com/path/to/dir,branch=stronk``.
71
The new ``bzr branches`` command can be used to list all present branches
72
in a directory, and indicates what the currently active branch is.
74
Several commands also accept co-located branch names directly, such as
80
All Bazaar formats now allow setting ``feature flags``. These can be used
81
by plugins to extend Bazaar formats and require the presence of particular
82
plugins or versions of Bazaar to open them, without having to introduce
83
completely new formats.
85
See ``doc/developers/feature-flags.txt`` for details.
90
Several commands or options that previously required access to the full
91
branch history now only access those parts of the history they actually
92
need. This significantly improves their performance for branches
98
A new command ``bzr verify-signatures`` can be used to verify GPG
99
signatures made with ``bzr commit`` or the ``bzr sign-my-commits``
105
Most error messages, help topics and other user-visible text can now be
106
translated. Initial translations for Russian, Japanese and Spanish exist.
111
The ``po_merge`` plugin has been added. It provides a merge hook
112
to automate merging of changes to gettext template files. Refer to
113
``bzr help po_merge`` for documentation on how to
114
enable it and what it can do.
19
116
Further information
20
117
*******************
added
removed
doc/en/whats-new/whats-new-in-2.5.txt
