Merge lp://qastaging/~jelmer/bzr/cmd-branches into lp://qastaging/bzr
Status: | Merged |
---|---|
Approved by: | Jelmer Vernooij |
Approved revision: | no longer in the source branch. |
Merged at revision: | 6082 |
Proposed branch: | lp://qastaging/~jelmer/bzr/cmd-branches |
Merge into: | lp://qastaging/bzr |
Diff against target: |
110 lines (+66/-2) 4 files modified
bzrlib/builtins.py (+17/-0) bzrlib/tests/blackbox/__init__.py (+1/-0) bzrlib/tests/blackbox/test_branches.py (+43/-0) doc/en/release-notes/bzr-2.5.txt (+5/-2) |
To merge this branch: | bzr merge lp://qastaging/~jelmer/bzr/cmd-branches |
Related bugs: |
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Jonathan Riddell (community) | Approve | ||
Review via email: mp+71577@code.qastaging.launchpad.net |
Commit message
Add a "bzr branches" command.
Description of the change
Add a 'bzr branches' command, which lists all of the colocated branches in a location.
This is different from the 'bzr branches' command that is currently present in bzrtools. It will currently only print the colocated branches in the specified location rather than looking for branches recursively.
This makes it reasonably easy to work with colocated branches. It would still be nice to add the functionality to look for branches by browsing the file system, but:
* that functionality is still present if bzrtools is installed (as bzrtools overrides the builtin "bzr branches" implementation)
* this needs API support, including refactoring of the existing BzrDir.
Why self.outf.write rather than trace.note() ?