Re: GIT_CONFIG - what's the point?
- From
Christian Couder <christian.couder@gmail.com>
- Date
- Apr 1, 2016, 11:19 UTC
- Message-ID
- <CAP8UFD23w_F8UtaykyY1KqE6Hee9355GZT+C29JL8EmYQCc6Yg@mail.gmail.com>
- In-Reply-To
- <CAL20dLDQsti1qW7CrrEifPAhPp1snq9r5MgJL+mDwhLqhe6fyQ@mail.gmail.com>
On Fri, Apr 1, 2016 at 2:54 AM, Matthew Persico <matthew.persico@gmail.com> wrote:
Show 9 quoted lines
> 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.