All of lore.kernel.org
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Jeff King <peff@peff.net>
Cc: "Cox\, Michael" <mhcox@bluezoosoftware.com>, git@vger.kernel.org
Subject: Re: How should git-config include.path option work in ~/.gitconfig file?
Date: Mon, 23 Jun 2014 10:36:15 -0700	[thread overview]
Message-ID: <xmqqegyfcyuo.fsf@gitster.dls.corp.google.com> (raw)
In-Reply-To: <20140621100803.GB16599@sigill.intra.peff.net> (Jeff King's message of "Sat, 21 Jun 2014 06:08:03 -0400")

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.

      parent reply	other threads:[~2014-06-23 17:36 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAK6hiNhumFhKd9tjr07SgtZe23LwW8RKSp3BbwVRh06-L0C8EA@mail.gmail.com>
2014-06-21 10:08 ` How should git-config include.path option work in ~/.gitconfig file? Jeff King
     [not found]   ` <CAK6hiNjxeQ6sy1Uk_ApTgKT41cPE-NB1D+ec2JqFvog_9HeFZw@mail.gmail.com>
2014-06-23 17:29     ` Jeff King
2014-06-23 17:36   ` Junio C Hamano [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=xmqqegyfcyuo.fsf@gitster.dls.corp.google.com \
    --to=gitster@pobox.com \
    --cc=git@vger.kernel.org \
    --cc=mhcox@bluezoosoftware.com \
    --cc=peff@peff.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.