Re: gitconfig includes

From: Eli Barzilay <eli@barzilay.org>
Date: Nov 29, 2016, 19:53 UTC
Message-ID: <CALO-gutJbM=LA3q8vdmbQJLoeCFAJWfPHFo8f1vz-5KJHVxJ6g@mail.gmail.com>
In-Reply-To: <xmqq7f7mf4rs.fsf@gitster.mtv.corp.google.com>

On Tue, Nov 29, 2016 at 2:46 PM, Junio C Hamano <gitster@pobox.com> wrote:

Show 11 quoted lines

> Eli Barzilay <eli@barzilay.org> writes:
>
>> So this is at least a documentation issue,...
>
> This already is documented, and I think it is clear enough.
>
>        --[no-]includes
>                   Respect include.* directives in config files when
>                   looking up values.  Defaults to off when a specific
>                   file is given (e.g., using --file, --global, etc)
>                   and on when searching all config files.

Yeah, that's clear, sorry for not checking the latest.

[I'd expect/wish it to be on by default though... Any reason for the default being off in these cases?]

-- 
                   ((x=>x(x))(x=>x(x)))                  Eli Barzilay:
                   http://barzilay.org/                  Maze is Life!