5
* New 'manifest' command and concept for making gpg-signatures
6
of revisions that are not tied to a particular internal
9
* Config options have moved from bzrlib.osutils to bzrlib.config.
10
Configuration is now done via the config.Config interface:
11
Depending on whether you have a Branch, a Location or no information
12
available, construct a *Config, and use its signature_checking,
13
username and user_email methods. (Robert Collins)
15
* Plugins are now loaded under bzrlib.plugins, not bzrlib.plugin, and
16
they are made available for other plugins to use. You should not
17
import other plugins during the __init__ of your plugin though, as
18
no ordering is guaranteed, and the plugins directory is not on the
24
* The config directory is now ~/.bazaar, and there is a single file
25
~/.bazaar/bazaar.conf storing email, editor and other preferences.
28
* 'bzr add' no longer takes a --verbose option, and a --quiet option
29
has been added that suppresses all output.
31
* 'bzr check' now accepts -v for verbose reporting, and checks for
37
* The --pattern option has been removed, now test specifiers on the
38
command line can be simple strings, or regexps, or both.
40
* Passing -v to selftest will now show the time each test took to
41
complete, which will aid in analysing performance regressions and
49
* Fix problem in pulling over http from machines that do not
50
allow directories to be listed.
52
* Avoid harmless warning about invalid hash cache after
53
upgrading branch format.
57
* Avoid some unnecessary http operations in branch and pull.
64
* 'bzr branch' over http initially gives a very high estimate
65
of completion time but it should fall as the first few
66
revisions are pulled in. branch is still slow on
67
high-latency connections.
71
* bzr-man.py has been updated to work again. Contributed by
74
* Locking is now done with fcntl.lockf which works with NFS
75
file systems. Contributed by Harald Meland.
77
* When a merge encounters a file that has been deleted on
78
one side and modified on the other, the old contents are
79
written out to foo.BASE and foo.SIDE, where SIDE is this
80
or OTHER. Contributed by Aaron Bentley.
82
* Export was choosing incorrect file paths for the content of
83
the tarball, this has been fixed by Aaron Bentley.
85
* Commit will no longer commit without a log message, an
86
error is returned instead. Contributed by Jelmer Vernooij.
88
* If you commit a specific file in a sub directory, any of its
89
parent directories that are added but not listed will be
90
automatically included. Suggested by Michael Ellerman.
92
* bzr commit and upgrade did not correctly record new revisions
93
for files with only a change to their executable status.
94
bzr will correct this when it encounters it. Fixed by
97
* HTTP tests now force off the use of http_proxy for the duration.
98
Contributed by Gustavo Niemeyer.
100
* Fix problems in merging weave-based branches that have
101
different partial views of history.
103
* Symlink support: working with symlinks when not in the root of a
104
bzr tree was broken, patch from Scott James Remnant.
109
* 'branch' now accepts a --basis parameter which will take advantage
110
of local history when making a new branch. This allows faster
111
branching of remote branches. Contributed by Aaron Bentley.
113
* New tree format based on weave files, called version 5.
114
Existing branches can be upgraded to this format using
117
* Symlinks are now versionable. Initial patch by
118
Erik Toubro Nielsen, updated to head by Robert Collins.
120
* Executable bits are tracked on files. Patch from Gustavo
123
* 'bzr status' now shows unknown files inside a selected directory.
124
Patch from Heikki Paajanen.
126
* Merge conflicts are recorded in .bzr. Two new commands 'conflicts'
127
and 'resolve' have needed added, which list and remove those
128
merge conflicts respectively. A conflicted tree cannot be committed
129
in. Contributed by Aaron Bentley.
131
* 'rm' is now an alias for 'remove'.
133
* Stores now split out their content in a single byte prefixed hash,
134
dropping the density of files per directory by 256. Contributed by
137
* 'bzr diff -r branch:URL' will now perform a diff between two branches.
138
Contributed by Robert Collins.
140
* 'bzr log' with the default formatter will show merged revisions,
141
indented to the right. Initial implementation contributed by Gustavo
142
Niemeyer, made incremental by Robert Collins.
147
* Test case failures have the exception printed after the log
148
for your viewing pleasure.
150
* InventoryEntry is now an abstract base class, use one of the
151
concrete InventoryDirectory etc classes instead.
153
* Branch raises an UnsupportedFormatError when it detects a
154
bzr branch it cannot understand. This allows for precise
155
handling of such circumstances.
160
* Removed testsweet module so that tests can be run after
161
bzr installed by 'bzr selftest'.
163
* 'bzr selftest' command-line arguments can now be partial ids
164
of tests to run, e.g. 'bzr selftest test_weave'
171
* Fixed "branch -r" option.
173
* Fix remote access to branches containing non-compressed history.
176
* Better reliability of http server tests. (John Arbash-Meinel)
178
* Merge graph maximum distance calculation fix. (Aaron Bentley)
180
* Various minor bug in windows support have been fixed, largely in the
181
test suite. Contributed by Alexander Belchenko.
185
* Status now accepts a -r argument to give status between chosen
186
revisions. Contributed by Heikki Paajanen.
188
* Revision arguments no longer use +/-/= to control ranges, instead
189
there is a 'before' namespace, which limits the successive namespace.
190
For example '$ bzr log -r date:yesterday..before:date:today' will
191
select everything from yesterday and before today. Contributed by
194
* There is now a bzr.bat file created by distutils when building on
195
Windows. Contributed by Alexander Belchenko.
199
* Removed uuid() as it was unused.
201
* Improved 'fetch' code for pulling revisions from one branch into
202
another (used by pull, merged, etc.)
209
* Adding a file whose parent directory is not versioned will
210
implicitly add the parent, and so on up to the root. This means
211
you should never need to explictly add a directory, they'll just
212
get added when you add a file in the directory. Contributed by
215
* Ignore .DS_Store (contains Mac metadata) by default. Patch from
218
* If you set BZR_EDITOR in the environment, it is checked in
219
preference to EDITOR and the config file for the interactive commit
220
editing program. Related to this is a bugfix where a missing program
221
set in EDITOR would cause editing to fail, now the fallback program
222
for the operating system is still tried.
224
* Files that are not directories/symlinks/regular files will no longer
225
cause bzr to fail, it will just ignore them by default. You cannot add
226
them to the tree though - they are not versionable.
231
* Refactor xml packing/unpacking.
235
* Fixed 'bzr mv' by Ollie Rutherfurd.
237
* Fixed strange error when trying to access a nonexistent http
240
* Make sure that the hashcache gets written out if it can't be
246
* Various Windows fixes from Ollie Rutherfurd.
248
* Quieten warnings about locking; patch from Matt Lavin.
255
* ``bzr shell-complete`` command contributed by Clint Adams to
256
help with intelligent shell completion.
258
* New expert command ``bzr find-merge-base`` for debugging merges.
263
* Much better merge support.
265
* merge3 conflicts are now reported with markers like '<<<<<<<'
266
(seven characters) which is the same as CVS and pleases things
272
* ``bzr upgrade`` no longer fails when trying to fix trees that
273
mention revisions that are not present.
275
* Fixed bugs in listing plugins from ``bzr plugins``.
277
* Fix case of $EDITOR containing options for the editor.
279
* Fix log -r refusing to show the last revision.
280
(Patch from Goffredo Baroncelli.)
285
* ``bzr log --show-ids`` shows the revision ids of all parents.
287
* Externally provided commands on your $BZRPATH no longer need
288
to recognize --bzr-usage to work properly, and can just handle
294
* Changed trace messages to go through the standard logging
295
framework, so that they can more easily be redirected by
added
removed
NEWS
