Re: Configuration overrides via environment variable
- From
- Jan Hudec <bulb@ucw.cz>
- Date
- Jan 28, 2008, 20:58 UTC
- Message-ID
- <20080128205837.GB5788@efreet.light.src>
- In-Reply-To
- <ee77f5c20801271708k124dc9d7n942b3c95299cb7fb@mail.gmail.com>
On Mon, Jan 28, 2008 at 12:08:10 +1100, David Symonds wrote:
Show 15 quoted lines
> Hi, > > I'm using Git in some scripts, and wanted to get its colorised output > even when it is not going to a tty. I don't want to permanently change > ~/.gitconfig or the per-repo config; I just want to set color.status > (and perhaps others) to "always" for a one-off run. I suppose I could > munge the config files, storing the previous value and restoring it > later, but that's messy. > > Ideally, an environment variable like GIT_EXTRA_CONFIG or something > would be nice, so I could just do: > > GIT_EXTRA_CONFIG="color.status=always" git status | ... > > Thoughts? Does this already exist, and I've overlooked it?
Quickly looking at the git-config manpage, there does not seem to be a way to provide alternate config file via GIT_CONFIG and/or GIT_CONFIG_LOCAL variables. I don't know how good match for your problem that would be.
-- Jan 'Bulb' Hudec <bulb@ucw.cz>