Jeff King 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_D
On Sun, Jun 22, 2014 at 01:00:53PM -0600, Cox, Michael wrote:
> I like the idea of recognizing environment variable syntax in config files,
> at least a feature that would allow *some* config variables to be specified
> as accepting environment variable syntax. It adds a lot of flexibility,
> but
[+cc mailing list]
On Sat, Jun 21, 2014 at 03:16:05AM -0600, Cox, Michael wrote:
> I discovered the new (to me, at least) git config include.path option
> recently and tried using it to include a file, .gitremotes in my git
> worktree. The .gitremotes file contains a remote.upstream section
> co
3 matches
Mail list logo
