Re: [PATCH 2/2] repo-config: learn the flag "--no-local"

From: Sean <seanlkml@sympatico.ca>
Date: Jun 8, 2006, 20:55 UTC
Message-ID: <BAYC1-PASMTP040660E676E00AD1631524AE8B0@CEZ.ICE>
In-Reply-To: <Pine.LNX.4.63.0606082235020.28405@wbgn013.biozentrum.uni-wuerzburg.de>

On Thu, 8 Jun 2006 22:42:17 +0200 (CEST) Johannes Schindelin <Johannes.Schindelin@gmx.de> wrote:

> I'd like to know how --home tells you when this key is retreived.

I honestly don't know.  How does --user tell you when this key is retrieved?

Show 11 quoted lines

> The admin has no business messing around with the users' configuration. 
> And if she absolutely wants to be a BOFH, she can fire up any editor, or 
> copy .gitconfig to /root/.gitconfig, use git-config, and copy it back, or 
> do what she does all the time: "su <user>". But frankly, we should not 
> support a bad work flow.
> 
> BTW it is the same reason I would rather not see /etc/gitconfig: it 
> meddles with an existing configuration. If you want to give defaults, you 
> can use a skeleton for $HOME, and templates for $GIT_DIR. As a user, I 
> would be very surprised if the behaviour of git changed from one day to 
> the other without my changing anything.

This seems like a rather heavy handed policy for an application to enforce. To my mind, these types of decisions are best left up to administrators; obviously we can't guess all the creative ways git will be used beforehand.

Sean