From: Johannes Schindelin Date: Sat, 19 Dec 2009 10:54:07 GMT Subject: Re: [PATCH] Introduce the GIT_CONFIG_EXTRA environment variable Message-ID: In-Reply-To: <4B2C7EC3.6070501@signalbeam.net> Hi, On Sat, 19 Dec 2009, Moe wrote: > What we do is, we put our entire runtime environment [for a web > application] under a dedicated user and under version control. This is a > very comfortable way to maintain an identical environment across the > board, we even deploy this way to our production servers by the means of > a git pull on a dedicated branch. Just ignoring the fact that you version control a version controlled directory (including the repository), which is inefficient, and even further ignoring the fact that you open the door for concurrent -- incompatible -- modifications, if all you want to do is: > In practice our developers will su or ssh to this user to get working > and generally they need only a very small set of divertions from the > common configuration - such as their personal git identity and their > preferred editor settings. ... then I suggest reading up on GIT_EDITOR, GIT_AUTHOR_IDENT and GIT_COMMITTER_IDENT, and leaving the $HOME/.gitconfig alone. Ciao, Dscho