19
* ``bzr commit`` accepts ``-p`` (for "patch") as a shorter name for
21
(Parth Malwankar, #571467)
23
* ``bzr ignore`` now supports a ``--default-rules`` option that displays
24
the default ignore rules used by bzr. The flag ``--old-default-rules``
25
is no longer supported by ``ignore``.
26
(Parth Malwankar, #538703)
28
* ``bzr pack`` now supports a ``--clean-obsolete-packs`` option that
29
can save disk space by deleting obsolete pack files created during the
31
(Parth Malwankar, #304320)
36
* ``.bazaar``, ``.bazaar/bazaar.conf`` and ``.bzr.log`` inherit user and
37
group ownership from the containing directory. This allow bzr to work
39
(Martin <gzlist@googlemail.com>, Parth Malwankar, #376388)
41
* ``bzr log --exclude-common-ancestry -r X..Y`` displays the revisions that
42
are part of Y ancestry but not part of X ancestry (aka the graph
44
(Vincent Ladeuil, #320119)
46
* ``bzr selftest --parallel=fork`` wait for its children avoiding zombies.
47
(Vincent Ladeuil, #566670)
49
* ``bzr selftest`` should not use ui.note() since it's not unicode safe.
50
(Vincent Ladeuil, #563997)
52
* Don't mention --no-strict when we just issue the warning about unclean trees.
53
(Vincent Ladeuil, #401599)
55
* Fixed ``AssertionError`` when accessing smart servers running Bazaar
57
(Andrew Bennetts, #528041)
59
22
* Reduce peak memory by one copy of compressed text.
60
23
(John Arbash Meinel, #566940)
62
* Show the filenames when a file rename fails so that the error will be
64
(Martin Pool, #491763)
69
* ``append_revisions_only`` will now be interpreted as a boolean and a
70
warning emitted if illegal values are used. Note that for projects
71
that needs to maintain compatibility with previsous bzr versions,
72
only 'True' and 'False' strings must be used (previous versions of
73
bzr will interpret all strings differing from 'True'
74
(case-sensitive) as false.
75
(Brian de Alwis, Vincent Ladeuil)
77
* ``Config.get_user_option_as_bool`` will now warn if a value cannot
78
be interpreted as a boolean.
87
* Added ``bzrlib.merge.PerFileMerger``, a more convenient way to write
88
some kinds of ``merge_file_content`` hook functions.
91
* `BzrDir`, `Branch`, `Repository` and `WorkingTree` now all support `user_url`,
92
`user_transport`, `control_url` and `control_transport` members pointing
93
respectively to the directory containing the ``.bzr`` control directory,
94
and to the directory within ``.bzr`` used for the particular component.
95
All of them inherit from `ControlComponent` which provides default
102
* ``_remember_remote_is_before`` no longer raises AssertionError when
103
suboptimal network behaviour is noticed; instead it just mutters to the
104
log file (and warns the user if they have set the ``hpss`` debug flag).
105
This was causing unnecessary aborts for performance bugs that are minor
107
(Andrew Bennetts, #528041)
109
37
* Permit bzr to run under ``python -OO`` which reduces the size of bytecode
110
38
files loaded from disk. To ensure docstrings needed for help are never
111
39
stripped, the prefix ``__doc__ =`` should now be used.
156
82
http://bugs.python.org/issue8396 .
157
83
(Parth Malwankar, #413406)
159
* ``bzr switch`` does not die if a ConfigurableFileMerger is used.
160
(Aaron Bentley, #559436)
162
85
* ``bzr update`` when a pending merge in the working tree has been merged
163
86
into the master branch will no longer claim that old commits have become
164
87
pending merges. (Robert Collins, #562079)
89
* ``bzr selftest --parallel=fork`` wait for its children avoiding zombies.
90
(Vincent Ladeuil, #566670)
166
92
* ``bzrlib.mutabletree.MutableTree.commit`` will now support a passed in
167
93
config as in previous versions of bzrlib. (Robert Collins)
95
* ``bzr selftest`` should not use ui.note() since it's not unicode safe.
96
(Vincent Ladeuil, #563997)
169
98
* Fix glitch in the warning about unclean trees display.
170
99
(Vincent Ladeuil, #562665)
181
110
which is not installed any more" error.
182
111
(Martin Pool, James Westby, #528114)
113
* Repositories accessed via a smart server now reject being stacked on a
114
repository in an incompatible format, as is the case when accessing them
115
via other methods. This was causing fetches from those repositories via
116
a smart server (e.g. using ``bzr branch``) to receive invalid data.
117
(Andrew Bennetts, #562380)
184
119
* Reset ``siginterrupt`` flag to False every time we handle a signal
185
120
installed with ``set_signal_handler(..., restart_syscall=True)`` (from
186
121
``bzrlib.osutils``. Reduces the likelihood of "Interrupted System Call"
527
463
happens, and another warning will be written if the log file could not
528
464
be closed after retrying 100 times. (Andrew Bennetts, #531746)
533
:2.1.2: NOT RELEASED YET
538
* ``bzr switch`` does not die if a ConfigurableFileMerger is used.
539
(Aaron Bentley, #559436)
541
* Fixed ``AssertionError`` when accessing smart servers running Bazaar
543
(Andrew Bennetts, #528041)
545
* Reset ``siginterrupt`` flag to False every time we handle a signal
546
installed with ``set_signal_handler(..., restart_syscall=True)`` (from
547
``bzrlib.osutils``. Reduces the likelihood of "Interrupted System Call"
548
errors after two window resizes.
554
* ``_remember_remote_is_before`` no longer raises AssertionError when
555
suboptimal network behaviour is noticed; instead it just mutters to the
556
log file (and warns the user if they have set the ``hpss`` debug flag).
557
This was causing unnecessary aborts for performance bugs that are minor
559
(Andrew Bennetts, #528041)
592
496
problems importing bzrlib from a non-main thread.
593
497
(Elliot Murphy, #521989)
595
* Repositories accessed via a smart server now reject being stacked on a
596
repository in an incompatible format, as is the case when accessing them
597
via other methods. This was causing fetches from those repositories via
598
a smart server (e.g. using ``bzr branch``) to receive invalid data.
599
(Andrew Bennetts, #562380)
601
499
* Standardize the error handling when creating a new ``StaticTuple``
602
500
(problems will raise TypeError). (Matt Nordhoff, #457979)
574
* ``append_revisions_only`` will no be interpreted as a boolean and a
575
warning emitted if illegal values are used. Note that for projects
576
that needs to maintain compatibility with previsous bzr versions,
577
only 'True' and 'False' strings must be used (previous versions of
578
bzr will interpret all strings differing from 'True'
579
(case-sensitive) as false.
580
(Brian de Alwis, Vincent Ladeuil)
582
* ``Config.get_user_option_as_bool`` will now warn if a value cannot
583
be interpreted as a boolean.
676
586
* Fetching into experimental formats will now print a warning. (Jelmer
added
removed
NEWS
