Should bzr aliases possibly be in their own file?

[Philip Peitsch]

This would actually be a major boon for enterprise management as well.  At
the moment I need to manually hack config files to get consistent setup for
using the coporate bzr repos (including usernames/emails, ssh
authentication, locations, plugins etc.).  A conf.d directory I would image
could make it much easier to simply place a site specific config in this
directory to provide a programmer with all the defaults generally used for
that project/site...

On Thu, Oct 14, 2010 at 10:00 AM, Martin Pool <mbp at canonical.com> wrote:

> Hi Tom,
>
> I think the desire to split up config files so they can be merged and
> copied doesn't need to be specific to aliases.  Perhaps we should have
> a conf.d directory, and read in the contents of all files within it.
>
> --
> Martin
>
>


-- 
Philip Peitsch
Mob: 0439 810 260
-------------- next part --------------
An HTML attachment was scrubbed...
URL: https://lists.ubuntu.com/archives/bazaar/attachments/20101014/b9f63cfb/attachment.htm