Re: Is there interest in reading ~/.gitconfig.d/* and /etc/gitconfig.d/*?

From: Jakub Narebski <jnareb@gmail.com>
Date: Apr 6, 2010, 09:02 UTC
Message-ID: <m36345hs4d.fsf@localhost.localdomain>
In-Reply-To: <u2i51dd1af81004060115t5f837840z5adcf83622fa8882@mail.gmail.com>

Ævar Arnfjörð Bjarmason <avarab@gmail.com> writes:

> On Sun, Apr 4, 2010 at 07:50, Eli Barzilay <eli@barzilay.org> wrote:

Show 14 quoted lines

> > Isn't it better to have a way to include files instead?
> 
> Probably yes. Programs like Apache HTTPD, rsyslog and others just use
> ${foo}conf.d by convention by supporting config inclusion.
> 
> What would be the ideal config syntax for that? AFAICT git-config
> doesn't (yet) support top-level keys so maybe this:
> 
>     [INCLUDE]
>         path = ~/.gitconfig.d/*
> 
> Or if top-level support was added:
> 
>     INCLUDE = ~/.gitconfig.d/*

<bikeshedding mode on>

I think that it would be better to use

        include ~/.gitconfig.d/*

<bikeshedding mode off>

-- 
Jakub Narebski
Poland
ShadeHawk on #git