Merge lp:~gagern/bzr/log_branch_from_revspec into lp:bzr
Status: | Work in progress |
---|---|
Proposed branch: | lp:~gagern/bzr/log_branch_from_revspec |
Merge into: | lp:bzr |
Diff against target: |
34 lines (+14/-0) 2 files modified
bzrlib/builtins.py (+1/-0) bzrlib/tests/blackbox/test_log.py (+13/-0) |
To merge this branch: | bzr merge lp:~gagern/bzr/log_branch_from_revspec |
Related bugs: |
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
John A Meinel | Needs Fixing | ||
Review via email: mp+28544@code.launchpad.net |
Commit message
Make the log command take its branch from the RevisionInfo.
Description of the change
This makes the bzr log builtin take the branch from the RevisionInfo, thereby allowing things like "bzr log -r -1:some/branch"
Unmerged revisions
- 5320. By Martin von Gagern
-
Merge branch from bug 149270.
That branch has already been approved, and the blackbox tests from both
branches would conflict. Now they can both be merged into bzr.dev. - 5319. By Martin von Gagern
-
Make the log command take its branch from the RevisionInfo.
This allows bzr log to operate with dwim revspecs that provide their own
branch although RevisionSpec_dwim doesn't override get_branch. Therefore
things like the "bzr log -r -1:some/branch" now start to work, as ensured by
the test case.They will still fail if the current dir doesn't have an associated bzr
branch, though, as it will still attempt to open a branch for the current
directory to be passed to the dwim revspec. In those cases, specifying the
prefix as in "-r revno:-1:some/ branch" would be a possible workaround.
sent to pqm by email