From: Christian Couder <christian.couder@gmail.com>
To: Matthew Persico <matthew.persico@gmail.com>
Cc: git <git@vger.kernel.org>
Subject: Re: GIT_CONFIG - what's the point?
Date: Fri, 1 Apr 2016 13:19:25 +0200 [thread overview]
Message-ID: <CAP8UFD23w_F8UtaykyY1KqE6Hee9355GZT+C29JL8EmYQCc6Yg@mail.gmail.com> (raw)
In-Reply-To: <CAL20dLDQsti1qW7CrrEifPAhPp1snq9r5MgJL+mDwhLqhe6fyQ@mail.gmail.com>
On Fri, Apr 1, 2016 at 2:54 AM, Matthew Persico
<matthew.persico@gmail.com> wrote:
> Greetings.
>
> Given the GIT_CONFIG environment variable can change 'git config'
> behaves, it stands to reason that if GIT_CONFIG is defined, then ALL
> git commands obey the value of GIT_CONFIG and use that file for config
> info.
>
> As a test, exported GIT_CONFIG=/tmp/ohm, copied ~/.gitconfig to
> /tmp/ohm,
Is /tmp/ohm a directory? If that is the case, then you should probably
have exported "GIT_CONFIG=/tmp/ohm/.gitconfig", as the git config doc
says it specifies a filename.
next prev parent reply other threads:[~2016-04-01 11:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-01 0:54 GIT_CONFIG - what's the point? Matthew Persico
2016-04-01 11:19 ` Christian Couder [this message]
2016-04-01 12:38 ` Jeff King
2016-04-01 14:31 ` Matthew Persico
2016-04-01 14:53 ` Jeff King
2016-04-01 17:28 ` SZEDER Gábor
2016-04-03 20:11 ` Matthew Persico
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=CAP8UFD23w_F8UtaykyY1KqE6Hee9355GZT+C29JL8EmYQCc6Yg@mail.gmail.com \
--to=christian.couder@gmail.com \
--cc=git@vger.kernel.org \
--cc=matthew.persico@gmail.com \
/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.