Config for branch, not in branch

[Vincent LADEUIL]

>>>>> "Jan" == Jan Hudec <bulb at ucw.cz> writes:

    Jan> Note, that the section name in ~/.bazaar/bazaar.conf is
    Jan> a *GLOB*. So if you always call foo branches
    Jan> foo.<something> and bar branches bar.<something>, you
    Jan> simply set the emails as:

I have just  begun to name my branches that  way, stop reading my
mind or I get a tinfoil hat :)

    Jan> [*/foo.*] email = me at foo.org
    Jan> [*/bar.*] email = me at bar.org

That's better. My gut feeling is  that it's still a bit weak, but
I can live with it (and  I have no better idea which indicates me
that I should just shut up :-)

    Jan> Of course, adapt to your naming convention.

    Jan> Note that the patterns are currently rather simplistic
    Jan> (* matches absolutely anything) and that it might be
    Jan> changed to behave more shell-like (* not matching / and
    Jan> initial . - **/ will then match any path).

I too call for an uniform  handling of globs, whatever it is (but
if it differs from basic  shell expansion, go for python regexps,
i.e. a clearly defined syntax instead of a custom one).

Thanks for your answers,

       Vincent