Combining branches.conf sections
Robert Collins
robertc at robertcollins.net
Sun Jan 15 22:20:59 GMT 2006
On Fri, 2006-01-13 at 14:48 +0100, Wouter van Heyst wrote:
> Hi all,
>
> yesterday I set up the email plugin to send commit mail to a mailing
> list for all branches in one dir, which worked and was great.
>
> [/home/larstiq/src/project/*]
> post_commit = bzrlib.plugins.email.post_commit
> post_commit_to = bzr-list at somehost
>
> However, after pushing one of those branches, mail stopped going out for
> that one. The added section in ~/.bazaar/branches.conf:
>
> [/home/larstiq/src/project/specific-branch]
> push_location = sftp://host/path
>
> http://bazaar.canonical.com/ConfiguringBzr explains why my globbing
> post_commit failed after push saved the push_location:
>
> For branches.conf, the variables from the section with the longest
> matching section header are used to the exclusion of other potentially
> valid section headers.
>
>
> So how to do this? Duplicating the post_commit stuff for each and every
> branch feels dirty, and I can't set under [DEFAULT] in bazaar.conf,
> because this is correct for one project only.
>
> So, what do people think of using information from all matching
> sections, applying in generic->specific order? The globbing is simple
> enough to not make debugging much harder.
Thats possible. I think there are two other routes though:
bzr push could copy the settings from the prior section
we could make inheritance optional.
I'm really ambivalent, this is a UI area where I'm not sure what the
right thing is..
Rob
--
GPG key available at: <http://www.robertcollins.net/keys.txt>.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part
Url : https://lists.ubuntu.com/archives/bazaar/attachments/20060116/f913060a/attachment.pgp
More information about the bazaar
mailing list