Hi, On Wed, 14 Feb 2007, Junio C Hamano wrote: > Johannes Schindelin <Johannes.Schindelin@xxxxxx> writes: > > > The settings in /etc/gitconfig can be overridden in ~/.gitconfig, > > which in turn can be overridden in .git/config. > > > > Signed-off-by: Johannes Schindelin <Johannes.Schindelin@xxxxxx> > > --- > > ... > > Voilà. > > I knew this can be done, and you are capable of doing this, but I was > wondering if it is a good thing to do in the first place. > > Site-wide configuration for options that are potentially > compatibility-breaking is a bad idea on a multi-user machines, and it > was certainly the case back when our machines hosted many diverse set of > people. That is why /etc is only writable by the administrator. And contrary to the Microsoft-infected world, Unix and Linux administrators are expected to have real know how. If they don't care about breaking things or not, they'll find other ways to screw you. > But these days many machines are practically single-user and many more > are owned by a single group/project that share the same policy. So in > such a setting, /etc/gitconfig might not be too bad. Well, I don't use it myself (other than testing that the patch does what it says). Let the list decide? Ciao, Dscho