Re: [PATCH] Introduce the GIT_CONFIG_EXTRA environment variable
- From
- Moe <moe@signalbeam.net>
- Date
- Dec 19, 2009, 11:38 UTC
- Message-ID
- <4B2CBB53.5000804@signalbeam.net>
- In-Reply-To
- <alpine.DEB.1.00.0912191150450.4985@pacific.mpi-cbg.de>
Johannes Schindelin wrote:
Show 14 quoted lines
> 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:
Neither is true.
Show 7 quoted lines
>> 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.
Thanks, that solved my problem. Seems I started by asking the wrong question.