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_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.
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to
More majordomo info at

Reply via email to