From: Johannes Schindelin <johannes.schindelin@gmx.de>
Date: Thu, 08 Jun 2006 12:21:55 GMT
Subject: Re: [PATCH 0/2] Introduce ~/.gitconfig
Message-ID: <Pine.LNX.4.63.0606081415380.26091@wbgn013.biozentrum.uni-wuerzburg.de>
In-Reply-To: <dbfc82860606080506y52dc2771sbf6c90e7246ca4c9@mail.gmail.com>

Hi,

On Thu, 8 Jun 2006, Nikolai Weibull wrote:

> On 6/8/06, Sven Ekman <svekman@yahoo.se> wrote:
> > <Johannes.Schindelin@gmx.de> skrev:
> > 
> > > There are three subjects for discussion:
> > 
> > Have you considered making ~/.gitconfig a directory?
> > Maybe Git wants to store more data later.
> 
> I second that.

I don't. What's wrong with the simple approach of a single config file? 
You can use a single tool for all the configuration, and do not need to 
care about anything.

After all, it is about _configuration_, not data storing. That is what 
$GIT_DIR/objects is for.

> And it'd be nice if it was configurable through an environment variable, 
> e.g., GIT_USER_CONFIG_HOME.

<sarcasm ignore=if-possible>
Let's see. AFAIK all programs I know (including cvs and vim, for 
one) have a fixed name. Hmm. Perhaps this is for a reason? Like, to reduce 
confusion?

Alternatively, we could introduce a config variable "core.globalConfig" to 
see where the global config is.
</sarcasm>

Ciao,
Dscho