From: David Aguilar <davvid@gmail.com>
To: Richard Purdie <rpurdie@rpsys.net>
Cc: "Junio C Hamano" <gitster@pobox.com>,
"Daniel Barkalow" <barkalow@iabervon.org>,
"Nguy� n Thái Ngọc Duy" <pclouds@gmail.com>,
"GIT Mailing-list" <git@vger.kernel.org>
Subject: Re: Overriding ~/.gitconfig using GIT_CONFIG
Date: Sun, 28 Aug 2011 06:05:56 -0700 [thread overview]
Message-ID: <20110828130555.GA56765@gmail.com> (raw)
In-Reply-To: <1313181853.14274.535.camel@rex>
On Fri, Aug 12, 2011 at 09:44:13PM +0100, Richard Purdie wrote:
> My problem isn't that I want to specify a specific .gitconfig file, I
> just need it to ignore the one in $HOME. I'm happy for the .git/config
> file to be used, in fact I need it to be.
If you're writing a tool then it should restrict itself to
git's plumbing commands. You should be able to do just about
anything without needing to worry about differences in
configuraiton. Git commands almost always provide a way to
override configuration through the use of flags.
The plumbing commands are listed in the main git manpage.
See "Low-level commands (plumbing)" here:
http://www.kernel.org/pub/software/scm/git/docs/
What is the specific problem solved by overriding the
configuration? It may be possible to solve it without needing
to get too complicated.
Have fun,
--
David
next prev parent reply other threads:[~2011-08-28 13:08 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-12 15:38 Overriding ~/.gitconfig using GIT_CONFIG Richard Purdie
2011-08-12 19:16 ` Junio C Hamano
2011-08-12 19:39 ` Junio C Hamano
2011-08-12 20:44 ` Richard Purdie
2011-08-28 13:05 ` David Aguilar [this message]
2011-08-29 12:16 ` Richard Purdie
2011-08-30 3:10 ` David Aguilar
2011-08-30 12:13 ` Richard Purdie
2011-08-30 15:56 ` Jeff King
2011-08-30 18:39 ` Richard Purdie
2011-08-30 18:49 ` Jeff King
2011-09-05 19:29 ` Richard Purdie
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=20110828130555.GA56765@gmail.com \
--to=davvid@gmail.com \
--cc=barkalow@iabervon.org \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=pclouds@gmail.com \
--cc=rpurdie@rpsys.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).