Merge lp:~jelmer/bzr/rmbranch-colo into lp:bzr
Proposed by
Jelmer Vernooij
Status: | Superseded | ||||
---|---|---|---|---|---|
Proposed branch: | lp:~jelmer/bzr/rmbranch-colo | ||||
Merge into: | lp:bzr | ||||
Diff against target: |
158 lines (+63/-17) (has conflicts) 4 files modified
bzrlib/builtins.py (+37/-14) bzrlib/tests/blackbox/test_rmbranch.py (+12/-2) bzrlib/tests/blackbox/test_switch.py (+1/-1) doc/en/release-notes/bzr-2.5.txt (+13/-0) Text conflict in doc/en/release-notes/bzr-2.5.txt |
||||
To merge this branch: | bzr merge lp:~jelmer/bzr/rmbranch-colo | ||||
Related bugs: |
|
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Martin Packman (community) | Needs Information | ||
Review via email: mp+94553@code.launchpad.net |
This proposal supersedes a proposal from 2012-02-23.
This proposal has been superseded by a proposal from 2012-02-28.
Description of the change
Support removing colocated branches in 'bzr rmbranch'.
Also includes a drive-by fix to reduce the number of HPSS connections for 'bzr switch' in lightweight checkouts by one.
To post a comment you must log in.
Substative changes all seems fine.
Is this intended to go on 2.5 or dev? Either needs retargetting or release notes need moving (and conflict to resolve there anyway).
-def lookup_ sibling_ branch( control_ dir, location, possible_ transports= None): branch( control_ dir, location, possible_ transports= None):
- """Lookup sibling branch.
-
+def open_sibling_
+ """Open a branch, possibly a sibling.
This looks technically like an api change if it's what's in 2.5.0 but as it's pretty new I guess it's okay to do.
- self.assertLeng th(2, self.hpss_calls) th(5, self.hpss_calls)
+ self.assertLeng
Sneaking this up is from looking at more possible branch locations?