From: Junio C Hamano <gitster@pobox.com>
Date: Mon, 23 Jun 2014 17:36:15 GMT
Subject: Re: How should git-config include.path option work in ~/.gitconfig file?
Message-ID: <xmqqegyfcyuo.fsf@gitster.dls.corp.google.com>
In-Reply-To: <20140621100803.GB16599@sigill.intra.peff.net>

Jeff King <peff@peff.net> writes:

> ... Recently we discussed supporting environment
> variables in expansions of path-oriented config variables. So something
> like:
>
>   [include]
>   path = $GIT_DIR/../.gitremotes
>
> would do what you want. We'd have to give some thought on what that
> should do when $GIT_DIR is not set (e.g., when you run a git command
> outside of a repository). I'd be inclined to say that such an include
> should be ignored (the naive shell interpretation would be to look for
> "/../.gitremotes", which is almost certainly not what the user wants).

I agree with everything in the above paragraph.
Thanks for forwarding.