All of lore.kernel.org
 help / color / mirror / Atom feed
From: Moe <moe@signalbeam.net>
To: "Shawn O. Pearce" <spearce@spearce.org>
Cc: Miklos Vajna <vmiklos@frugalware.org>,
	Junio C Hamano <gitster@pobox.com>,
	git@vger.kernel.org
Subject: Re: [PATCH] Introduce the GIT_CONFIG_EXTRA environment variable
Date: Sat, 19 Dec 2009 04:06:08 +0100	[thread overview]
Message-ID: <4B2C4320.6060007@signalbeam.net> (raw)
In-Reply-To: <20091219020947.GB10687@spearce.org>

Shawn O. Pearce wrote:
> Miklos Vajna <vmiklos@frugalware.org> wrote:
>> This is like GIT_CONFIG but it is not read instead of .git/config, but
>> in addtition to it.
> 
> What file does `git config --add` modify?  Should we be able to
> modify the GIT_CONFIG_EXTRA file?

>From my use-case corner: Yes, this would basically be used
to divert ~/.gitconfig and should behave in all the same ways.

> What order is GIT_CONFIG_EXTRA applied in relative to other files
> that git config would also have read?

This is up to Miklos to answer but again from my use-case angle it would
make the most sense to read the usual config files first
and GIT_CONFIG_EXTRA last - that way the user config gets the
last word in terms of overriding global and repository defaults.

And btw, thanks for the fast action Miklos!


Kind regards,
Moe

  reply	other threads:[~2009-12-19  3:06 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-18 22:54 FEATURE REQUEST: Env override GIT_GLOBAL_CONFIG Moe
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 [this message]
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=4B2C4320.6060007@signalbeam.net \
    --to=moe@signalbeam.net \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=spearce@spearce.org \
    --cc=vmiklos@frugalware.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.