From: Peter Baumann <siprbaum@stud.informatik.uni-erlangen.de>
Date: Wed, 14 Feb 2007 10:30:09 GMT
Subject: Re: /etc/gitconfig
Message-ID: <slrnet5p5h.s9h.siprbaum@xp.machine.xx>
In-Reply-To: <200702140909.28369.andyparkins@gmail.com>

Andy Parkins <andyparkins@gmail.com> schrieb:
> Hello
>
> With the release of 1.5.0 I added legacyheaders=false and 
> usedelatbaseoffset=true to my repositories.
>
> While doing that though, it felt wrong to be editing every single config.  Is 
> there a justification for having three config files?
>
>  /etc/gitconfig
>  $HOME/.gitconfig
>  $GIT_DIR/config
>
> With /etc/gitconfig coming in at lowest priority?
>
> Andy

I would like this, too. This would allow me to set e.g.
"diff.color = auto" for everyone one a machine. We use git there to only
manage some config files and several simple perl scripts. As it is
mostly myself who does the editing, ~/.gitconfig works for *ME*.

But I'd like to set this globally so that my colluagues which don't have
much clue about git don't need to bother about config settings. And yes,
editing every single repo doesn't seem like an elegant solution. 

-Peter