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

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Ævar Arnfjörð Bjarmason <avarab@xxxxxxxxx> writes:
> On Sun, Apr 4, 2010 at 07:50, Eli Barzilay <eli@xxxxxxxxxxxx> wrote:

> > 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
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Linux Kernel Development]     [Gcc Help]     [IETF Annouce]     [DCCP]     [Netdev]     [Networking]     [Security]     [V4L]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux SCSI]     [Fedora Users]