From: "Bradford Smith" <bradford.carl.smith@gmail.com>
To: "Nikolai Weibull" <now@bitwi.se>
Cc: git@vger.kernel.org
Subject: Re: git-config: replaces ~/.gitconfig symlink with real file
Date: Mon, 16 Jul 2007 09:26:01 -0400 [thread overview]
Message-ID: <f158199e0707160626j1025ab2cp3339ca6ab91d9af0@mail.gmail.com> (raw)
In-Reply-To: <f158199e0707160433v27fe7073w9c550712c41c32e8@mail.gmail.com>
On 7/16/07, Bradford Smith <bradford.carl.smith@gmail.com> wrote:
> On 7/16/07, Nikolai Weibull <now@bitwi.se> wrote:
> > On 7/15/07, Bradford Smith <bradford.carl.smith@gmail.com> wrote:
> > > Since the number of dot-files and dot-directories that I have in my
> > > home directory these days is somewhat overwhelming, I like to keep
> > > those I directly edit all together in an ~/etc directory so I can
> > > easily back them up and/or copy them in bulk to new accounts. So,
> > > several of my home dot-files are just symlinks to something in ~/etc,
> > > including ~/.gitconfig.
> >
> > How about adding an environment variable telling Git where to find
> > user-global .gitconfig instead?
> > > home directory these days is somewhat overwhelming, I like to keep
> > > those I directly edit all together in an ~/etc directory so I can
> > > easily back them up and/or copy them in bulk to new accounts. So,
> > > several of my home dot-files are just symlinks to something in ~/etc,
> > > including ~/.gitconfig.
> >
> > How about adding an environment variable telling Git where to find
> > user-global .gitconfig instead?
>
> Thanks for suggesting that.
>
> Actually, by looking at the code I discovered I could use the
> environment variable GIT_CONFIG to specify where the configuration
> file is, and I have already changed my setup to use this.
> Unfortunately, I found the documentation for this variable in
> git-config(1) confusing or I would have used it before. If I get the
> chance, I'll submit a patch for git-config.txt, and maybe for git.txt
> as well, since it lists lots of other environment variables but not
> GIT_CONFIG or GIT_CONFIG_LOCAL.
>
> Thanks,
>
> Bradford
>
Drat! The documentation wasn't as wrong as I had hoped. If I set
GIT_CONFIG, git will ignore $(prefix)/etc/gitconfig and ~/.git/config,
which isn't what I want. So, I guess I need to add a GIT_CONFIG_HOME
environment variable. If I get that done, I'll send a patch to the
list including doc updates.
Of course, if someone else wants to do it first, I won't complain. B')
Thanks,
Bradford
next prev parent reply other threads:[~2007-07-16 13:27 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-15 21:27 git-config: replaces ~/.gitconfig symlink with real file Bradford Smith
2007-07-15 23:30 ` Johannes Schindelin
2007-07-16 9:37 ` Nikolai Weibull
2007-07-16 11:33 ` Bradford Smith
2007-07-16 13:26 ` Bradford Smith [this message]
2007-07-16 22:46 ` Junio C Hamano
2007-07-25 16:49 ` [PATCH 0/2] git-config should not replace symlink Bradford C. Smith
2007-07-25 16:49 ` [PATCH 1/2] resolve symlinks when creating lockfiles Bradford C. Smith
2007-07-25 16:49 ` [PATCH 2/2] use lockfile.c routines in git_commit_set_multivar() Bradford C. Smith
2007-07-25 23:35 ` [PATCH 1/2] resolve symlinks when creating lockfiles Junio C Hamano
2007-07-26 16:55 ` [PATCH] use lockfile.c routines in git_commit_set_multivar() Bradford C. Smith
2007-07-26 18:31 ` Johannes Schindelin
2007-07-26 18:48 ` Bradford Smith
2007-07-27 4:30 ` Junio C Hamano
2007-07-27 4:53 ` Junio C Hamano
2007-07-27 9:05 ` Johannes Schindelin
2007-07-27 18:24 ` Bradford Smith
2007-07-26 17:34 ` [PATCH] fully resolve symlinks when creating lockfiles Bradford C. Smith
2007-07-26 18:35 ` Johannes Schindelin
2007-07-26 19:34 ` Morten Welinder
2007-07-27 16:50 ` Bradford Smith
2007-07-27 7:05 ` Junio C Hamano
2007-07-17 13:56 ` git-config: replaces ~/.gitconfig symlink with real file Johannes Schindelin
2007-07-17 14:27 ` Matthieu Moy
2007-07-17 20:35 ` Fredrik Tolf
2007-07-17 20:48 ` Johannes Schindelin
2007-07-17 13:39 ` Catalin Marinas
2007-07-17 16:09 ` Johannes Schindelin
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=f158199e0707160626j1025ab2cp3339ca6ab91d9af0@mail.gmail.com \
--to=bradford.carl.smith@gmail.com \
--cc=git@vger.kernel.org \
--cc=now@bitwi.se \
/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).