5
* Adding a file whose parent directory is not versioned will
6
implicitly add the parent, and so on up to the root. This means
7
you should never need to explictly add a directory, they'll just
8
get added when you add a file in the directory. Contributed by
14
* Refactor xml packing/unpacking.
19
* Fixed 'bzr mv' by Ollie Rutherfurd.
21
* Fixed strange error when trying to access a nonexistent http
24
* Make sure that the hashcache gets written out if it can't be
30
* Various Windows fixes from Ollie Rutherfurd.
37
* ``bzr shell-complete`` command contributed by Clint Adams to
38
help with intelligent shell completion.
40
* New expert command ``bzr find-merge-base`` for debugging merges.
45
* Much better merge support.
47
* merge3 conflicts are now reported with markers like '<<<<<<<'
48
(seven characters) which is the same as CVS and pleases things
54
* ``bzr upgrade`` no longer fails when trying to fix trees that
55
mention revisions that are not present.
57
* Fixed bugs in listing plugins from ``bzr plugins``.
59
* Fix case of $EDITOR containing options for the editor.
61
* Fix log -r refusing to show the last revision.
62
(Patch from Goffredo Baroncelli.)
67
* ``bzr log --show-ids`` shows the revision ids of all parents.
69
* Externally provided commands on your $BZRPATH no longer need
70
to recognize --bzr-usage to work properly, and can just handle
76
* Changed trace messages to go through the standard logging
77
framework, so that they can more easily be redirected by
86
* Python plugins, automatically loaded from the directories on
87
BZR_PLUGIN_PATH or ~/.bzr.conf/plugins by default.
89
* New 'bzr mkdir' command.
91
* Commit mesage is fetched from an editor if not given on the
92
command line; patch from Torsten Marek.
94
* ``bzr log -m FOO`` displays commits whose message matches regexp
97
* ``bzr add`` with no arguments adds everything under the current directory.
99
* ``bzr mv`` does move or rename depending on its arguments, like
102
* ``bzr missing`` command shows a summary of the differences
103
between two trees. (Merged from John Arbash-Meinel.)
105
* An email address for commits to a particular tree can be
106
specified by putting it into .bzr/email within a branch. (Based
107
on a patch from Heikki Paajanen.)
112
* Faster working tree operations.
117
* 3rd-party modules shipped with bzr are copied within the bzrlib
118
python package, so that they can be installed by the setup
119
script without clashing with anything already existing on the
120
system. (Contributed by Gustavo Niemeyer.)
122
* Moved plugins directory to bzrlib/, so that there's a standard
123
plugin directory which is not only installed with bzr itself but
124
is also available when using bzr from the development tree.
125
BZR_PLUGIN_PATH and DEFAULT_PLUGIN_PATH are then added to the
126
standard plugins directory.
128
* When exporting to a tarball with ``bzr export --format tgz``, put
129
everything under a top directory rather than dumping it into the
130
current directory. This can be overridden with the ``--root``
131
option. Patch from William Dodé and John Meinel.
133
* New ``bzr upgrade`` command to upgrade the format of a branch,
134
replacing ``bzr check --update``.
136
* Files within store directories are no longer marked readonly on
139
* Changed ``bzr log`` output to a more compact form suggested by
140
John A Meinel. Old format is available with the ``--long`` or
141
``-l`` option, patched by William Dodé.
143
* By default the commit command refuses to record a revision with
144
no changes unless the ``--unchanged`` option is given.
146
* The ``--no-plugins``, ``--profile`` and ``--builtin`` command
147
line options must come before the command name because they
148
affect what commands are available; all other options must come
149
after the command name because their interpretation depends on
152
* ``branch`` and ``clone`` added as aliases for ``branch``.
154
* Default log format is back to the long format; the compact one
155
is available with ``--short``.
160
* Fix bugs in committing only selected files or within a subdirectory.
167
* ``bzr`` with no command now shows help rather than giving an
168
error. Suggested by Michael Ellerman.
170
* ``bzr status`` output format changed, because svn-style output
171
doesn't really match the model of bzr. Now files are grouped by
172
status and can be shown with their IDs. ``bzr status --all``
173
shows all versioned files and unknown files but not ignored files.
175
* ``bzr log`` runs from most-recent to least-recent, the reverse
176
of the previous order. The previous behaviour can be obtained
177
with the ``--forward`` option.
179
* ``bzr inventory`` by default shows only filenames, and also ids
180
if ``--show-ids`` is given, in which case the id is the second
1
bzr-0.0.5 NOT RELEASED YET
186
5
* New 'bzr whoami --email' option shows only the email component
187
6
of the user identification, from Jo Vermeulen.
189
* New ``bzr ignore PATTERN`` command.
191
* Nicer error message for broken pipe, interrupt and similar
192
conditions that don't indicate an internal error.
194
* Add ``.*.sw[nop] .git .*.tmp *,v`` to default ignore patterns.
196
* Per-branch locks keyed on ``.bzr/branch-lock``, available in
197
either read or write mode.
199
* New option ``bzr log --show-ids`` shows revision and file ids.
201
* New usage ``bzr log FILENAME`` shows only revisions that
204
* Changed format for describing changes in ``bzr log -v``.
206
* New option ``bzr commit --file`` to take a message from a file,
207
suggested by LarstiQ.
209
* New syntax ``bzr status [FILE...]`` contributed by Bartosz
210
Oler. File may be in a branch other than the working directory.
212
* ``bzr log`` and ``bzr root`` can be given an http URL instead of
215
* Commands can now be defined by external programs or scripts
216
in a directory on $BZRPATH.
218
* New "stat cache" avoids reading the contents of files if they
219
haven't changed since the previous time.
221
* If the Python interpreter is too old, try to find a better one
222
or give an error. Based on a patch from Fredrik Lundh.
224
* New optional parameter ``bzr info [BRANCH]``.
226
* New form ``bzr commit SELECTED`` to commit only selected files.
228
* New form ``bzr log -r FROM:TO`` shows changes in selected
229
range; contributed by John A Meinel.
231
* New option ``bzr diff --diff-options 'OPTS'`` allows passing
232
options through to an external GNU diff.
234
* New option ``bzr add --no-recurse`` to add a directory but not
237
* ``bzr --version`` now shows more information if bzr is being run
243
* Fixed diff format so that added and removed files will be
244
handled properly by patch. Fix from Lalo Martins.
246
* Various fixes for files whose names contain spaces or other
252
* Converted black-box test suites from Bourne shell into Python;
253
now run using ``./testbzr``. Various structural improvements to
256
* testbzr by default runs the version of bzr found in the same
257
directory as the tests, or the one given as the first parameter.
259
* testbzr also runs the internal tests, so the only command
260
required to check is just ``./testbzr``.
262
* testbzr requires python2.4, but can be used to test bzr running
263
under a different version.
265
* Tests added for many other changes in this release.
270
* Included ElementTree library upgraded to 1.2.6 by Fredrik Lundh.
272
* Refactor command functions into Command objects based on HCT by
275
* Better help messages for many commands.
277
* Expose bzrlib.open_tracefile() to start the tracefile; until
278
this is called trace messages are just discarded.
280
* New internal function find_touching_revisions() and hidden
281
command touching-revisions trace the changes to a given file.
283
* Simpler and faster compare_inventories() function.
285
* bzrlib.open_tracefile() takes a tracefilename parameter.
287
* New AtomicFile class.
289
* New developer commands ``added``, ``modified``.
294
* Cope on Windows on python2.3 by using the weaker random seed.
295
2.4 is now only recommended.
298
9
bzr-0.0.4 2005-04-22
added
removed
NEWS
