git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ramkumar Ramachandra <artagnon@gmail.com>
To: Jeff King <peff@peff.net>
Cc: Git List <git@vger.kernel.org>, David Aguilar <davvid@gmail.com>,
	Anurag Priyam <anurag08priyam@gmail.com>,
	Junio C Hamano <gitster@pobox.com>
Subject: Re: [PATCH] config: introduce GIT_GLOBAL_CONFIG to override ~/.gitconfig
Date: Fri, 28 Sep 2012 12:35:31 +0530	[thread overview]
Message-ID: <CALkWK0=CCLrfM2Jr_JNVP0VQnp1dvRAkDjRrTsogvpD8rGrumw@mail.gmail.com> (raw)
In-Reply-To: <20120927173532.GD1547@sigill.intra.peff.net>

Jeff King wrote:
> Like the other reviews, I am not overly enthused. If we are going to add
> a new variable, I think $GIT_HOME makes a lot more sense. But it really
> sounds like using $XDG_CONFIG_HOME would be even simpler.
>
> Also, have you considered using a config include? Like:
>
>   $ echo '[include]path = ~/my-dotfiles/gitconfig' >~/.gitconfig

Sounds like this is the way to go.  Or I could pick up Junio's
suggestion to use a Makefile.  I'll discontinue working on the patch.

Thanks.

Ram

  parent reply	other threads:[~2012-09-28  7:06 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-26 14:14 Configuring the location of ~/.gitconfig Ramkumar Ramachandra
2012-09-26 18:34 ` David Aguilar
2012-09-27  6:49   ` Ramkumar Ramachandra
2012-09-27 14:46     ` [PATCH] config: introduce GIT_GLOBAL_CONFIG to override ~/.gitconfig Ramkumar Ramachandra
2012-09-27 16:57       ` Matthieu Moy
2012-09-27 17:50         ` Junio C Hamano
2012-09-27 17:27       ` Junio C Hamano
2012-09-27 17:35       ` Jeff King
2012-09-27 19:57         ` Junio C Hamano
2012-09-27 20:51         ` Matthieu Moy
2012-09-28  7:05         ` Ramkumar Ramachandra [this message]
2012-09-27  6:09 ` Configuring the location of ~/.gitconfig Junio C Hamano
2012-09-27  6:40   ` Anurag Priyam
2012-09-27 17:16     ` Junio C Hamano

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='CALkWK0=CCLrfM2Jr_JNVP0VQnp1dvRAkDjRrTsogvpD8rGrumw@mail.gmail.com' \
    --to=artagnon@gmail.com \
    --cc=anurag08priyam@gmail.com \
    --cc=davvid@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=peff@peff.net \
    /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).