Merge lp:~abentley/bzr/config-branchname into lp:bzr
Status: | Merged |
---|---|
Approved by: | John A Meinel |
Approved revision: | no longer in the source branch. |
Merged at revision: | 6526 |
Proposed branch: | lp:~abentley/bzr/config-branchname |
Merge into: | lp:bzr |
Diff against target: |
111 lines (+49/-4) 3 files modified
bzrlib/config.py (+14/-4) bzrlib/help_topics/en/configuration.txt (+12/-0) bzrlib/tests/test_config.py (+23/-0) |
To merge this branch: | bzr merge lp:~abentley/bzr/config-branchname |
Related bugs: |
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
John A Meinel | Approve | ||
Review via email: mp+110825@code.launchpad.net |
Commit message
Support branchname config variable.
Description of the change
This branch adds a "branchname" automatic config variable, which is the name of a native colocated branch, as specified by the "branch=" portion of its url. This allows the user to configure urls to reflect the branch name, just as they would use relpath or basename to configure other types of branches.
I have used it like so, in order to push this branch:
[/home/
push_location = bzr+ssh:
This is an itch that I am scratching. For me, the biggest advantage of bzr-colo colocation is that, since it uses standard branches, it can automatically configure the push and public locations. With this change, native colo branches will have parity in terms of configuration.
On Mon, 18 Jun 2012 14:00:27 -0000, Aaron Bentley <email address hidden> wrote:
> +Another such option is ``branchname``, which refers to the name of a colocated
> +branch. It can be used like this::
Is it just colocated branches, or does it work for all local branches?
It seems like this could work for pipelines with much the same
configuration if it does?
Thanks,
James