From: Moe <moe@signalbeam.net>
To: git@vger.kernel.org
Subject: FEATURE REQUEST: Env override GIT_GLOBAL_CONFIG
Date: Fri, 18 Dec 2009 23:54:32 +0100 [thread overview]
Message-ID: <4B2C0828.4010505@signalbeam.net> (raw)
Hello list,
I'm looking for a way to read a custom config file in
addition to .git/config.
An env var along the lines of GIT_GLOBAL_CONFIG (and perhaps
GIT_SYSTEM_CONFIG) to override the default locations of
~/.gitconfig or $prefix/etc/gitconfig would be most
welcome here.
$GIT_CONFIG doesn't work for this purpose because when set
git will *only* read the referenced file and ignore the
repository settings.
$GIT_CONFIG_LOCAL wouldn't do either and has been
removed from git anyways.
Use-Case:
Multiple users sharing one unix account. Trying to inject the respective
git identity and other preferences without overwriting
the actual .gitconfig-file - because that doesn't work when multiple
users are logged in concurrently to the same unix-account.
Kind regards,
Moe
next reply other threads:[~2009-12-18 22:54 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-18 22:54 Moe [this message]
2009-12-19 1:32 ` [PATCH] Introduce the GIT_CONFIG_EXTRA environment variable Miklos Vajna
2009-12-19 2:09 ` Shawn O. Pearce
2009-12-19 3:06 ` Moe
2009-12-19 14:25 ` Miklos Vajna
2009-12-19 3:24 ` Junio C Hamano
2009-12-19 4:44 ` Moe
2009-12-19 5:55 ` Junio C Hamano
2009-12-19 7:20 ` Moe
2009-12-19 10:54 ` Johannes Schindelin
2009-12-19 11:38 ` Moe
2009-12-19 14:45 ` Nanako Shiraishi
2009-12-19 15:30 ` [PATCH] Introduce the GIT_HOME " Miklos Vajna
2009-12-19 16:18 ` Michael J Gruber
2009-12-19 16:44 ` Miklos Vajna
2009-12-19 17:10 ` Matthieu Moy
2009-12-19 19:13 ` Junio C Hamano
2009-12-21 10:25 ` Matthieu Moy
2009-12-21 15:59 ` Jeff King
2009-12-21 16:26 ` Matthieu Moy
2009-12-21 16:54 ` Michael J Gruber
2009-12-19 19:21 ` Junio C Hamano
2009-12-20 0:34 ` Miklos Vajna
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=4B2C0828.4010505@signalbeam.net \
--to=moe@signalbeam.net \
--cc=git@vger.kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).