Re: [PATCH 0/2] Introduce ~/.gitconfig

From: Johannes Schindelin <johannes.schindelin@gmx.de>
Date: Jun 8, 2006, 15:19 UTC
Message-ID: <Pine.LNX.4.63.0606081711520.27335@wbgn013.biozentrum.uni-wuerzburg.de>
In-Reply-To: <1149775348.23938.236.camel@cashmere.sps.mot.com>

Hi,

On Thu, 8 Jun 2006, Jon Loeliger wrote:

Show 15 quoted lines

> On Thu, 2006-06-08 at 06:30, Johannes Schindelin wrote:
> 
> > - The --no-local flag could be implemented more cleanly, but also less
> 
> Could we have multiple levels, and have names that call out
> where it applies?  Perhaps something like:
> 
> --repo   into $GIT_DIR/.gitconfig  <- current default, right?
> --home   into ~/.gitconfig
> --site   into /etc/gitconfig
> --share  into /usr/share/git/config
> 
> My issue is that --no-local is vague and doesn't call out
> where it actually does go.  There could be more than one
> different non-local place.

The whole idea is that there are only two levels of configuration. Global (applies to all calls to git) and local (applies only to the repository).

Now, it makes sense to make settings overrideable in a certain order: If the global default does not match your needs in a particular case, override it. With "git-repo-config <key> <value>".

*However*, if you want to change the default, it makes sense to say "--no-local" or "--global", but I doubt that it makes any sense at all to access a certain finer level. For example, when would you possibly need to wrap in porcelain a method to query exactly which aliases are defined in /usr/local/share/git/config?

IOW if you want to edit /etc/gitconfig or something else you need admin permissions for with git-repo-config, you should look for another profession. Quickly.

> But, hey, that's all pre-coffee.

post-coffee is pre-coffee.

Ciao, Dscho