From: Andy Parkins <andyparkins@gmail.com>
To: git@vger.kernel.org
Cc: Junio C Hamano <junkio@cox.net>,
Johannes Schindelin <Johannes.Schindelin@gmx.de>,
Peter Baumann <siprbaum@stud.informatik.uni-erlangen.de>
Subject: Re: [PATCH] config: read system-wide defaults from /etc/gitconfig
Date: Thu, 15 Feb 2007 10:19:24 +0000 [thread overview]
Message-ID: <200702151019.25409.andyparkins@gmail.com> (raw)
In-Reply-To: <7vfy98snus.fsf@assigned-by-dhcp.cox.net>
On Wednesday 2007 February 14 16:30, Junio C Hamano wrote:
> 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.
Isn't it more likely that on a multi-user machine all users are sharing one
install of git - in which case you do want the upgrade of facilities to be
system-wide. Otherwise you have to tell every user to edit their .gitconfig
to enable the new facilities - users shouldn't have to care about that sort
of thing, that's what admins are for.
Andy
--
Dr Andy Parkins, M Eng (hons), MIEE
andyparkins@gmail.com
next prev parent reply other threads:[~2007-02-15 10:19 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-14 9:09 /etc/gitconfig Andy Parkins
2007-02-14 10:30 ` /etc/gitconfig Peter Baumann
2007-02-14 11:48 ` [PATCH] config: read system-wide defaults from /etc/gitconfig Johannes Schindelin
2007-02-14 16:30 ` Junio C Hamano
2007-02-14 17:45 ` Johannes Schindelin
2007-02-14 17:57 ` Junio C Hamano
2007-02-14 18:02 ` Johannes Schindelin
2007-02-14 18:12 ` Junio C Hamano
2007-02-14 18:19 ` Nicolas Pitre
2007-02-14 19:06 ` Junio C Hamano
2007-02-15 10:19 ` Andy Parkins [this message]
2007-02-15 11:26 ` Junio C Hamano
[not found] ` <20070215113557.GB2282@steel.home>
[not found] ` <20070216143952.GA2478@steel.home>
2007-02-16 14:42 ` [PATCH] Allow config files to be included Alex Riesen
2007-02-16 14:45 ` Alex Riesen
2007-02-14 18:10 ` [PATCH] config: read system-wide defaults from /etc/gitconfig Han-Wen Nienhuys
2007-02-14 19:07 ` Junio C Hamano
2007-02-14 19:25 ` Johannes Schindelin
2007-02-14 19:43 ` Junio C Hamano
2007-02-14 19:54 ` Johannes Schindelin
2007-02-14 22:39 ` Johannes Schindelin
2007-02-15 5:27 ` Junio C Hamano
2007-02-15 8:46 ` Junio C Hamano
2007-02-15 9:59 ` Eric Wong
2007-02-15 10:03 ` Eric Wong
2007-02-15 10:36 ` Junio C Hamano
2007-02-15 10:43 ` Johannes Schindelin
2007-02-15 11:25 ` Junio C Hamano
2007-02-15 12:05 ` Johannes Schindelin
2007-02-19 1:47 ` Jakub Narebski
2007-02-14 10:40 ` /etc/gitconfig Uwe Kleine-König
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200702151019.25409.andyparkins@gmail.com \
--to=andyparkins@gmail.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
--cc=siprbaum@stud.informatik.uni-erlangen.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.