← Back to branch summary

~bzr-pqm/bzr/bzr.dev

« back to all changes in this revision

Viewing changes to NEWS

  • Committer: Robert Collins
  • Date: 2010-05-06 23:41:35 UTC
  • mto: This revision was merged to the branch mainline in revision 5223.
  • Revision ID: robertc@robertcollins.net-20100506234135-yivbzczw1sejxnxc
Lock methods on ``Tree``, ``Branch`` and ``Repository`` are now
expected to return an object which can be used to unlock them. This reduces
duplicate code when using cleanups. The previous 'tokens's returned by
``Branch.lock_write`` and ``Repository.lock_write`` are now attributes
on the result of the lock_write. ``repository.RepositoryWriteLockResult``
and ``branch.BranchWriteLockResult`` document this. (Robert Collins)

``log._get_info_for_log_files`` now takes an add_cleanup callable.
(Robert Collins)

Show diffs side-by-side

added added

removed removed

Lines of Context:
NEWS
96
96
  implementations.
97
97
  (Martin Pool)
98
98
 
 
99
* Lock methods on ``Tree``, ``Branch`` and ``Repository`` are now
 
100
  expected to return an object which can be used to unlock them. This reduces
 
101
  duplicate code when using cleanups. The previous 'tokens's returned by
 
102
  ``Branch.lock_write`` and ``Repository.lock_write`` are now attributes
 
103
  on the result of the lock_write. ``repository.RepositoryWriteLockResult``
 
104
  and ``branch.BranchWriteLockResult`` document this. (Robert Collins)
 
105
 
99
106
Internals
100
107
*********
101
108
 
 
109
* ``log._get_info_for_log_files`` now takes an add_cleanup callable.
 
110
  (Robert Collins)
 
111
 
102
112
* ``_remember_remote_is_before`` no longer raises AssertionError when
103
113
  suboptimal network behaviour is noticed; instead it just mutters to the
104
114
  log file (and warns the user if they have set the ``hpss`` debug flag).