From: Yaroslav Halchenko <yoh@onerussian.com>
To: Jeff King <peff@peff.net>
Cc: Jacob Keller <jacob.keller@gmail.com>,
"brian m. carlson" <sandals@crustytoothpaste.net>,
Junio C Hamano <gitster@pobox.com>,
Jonathan Nieder <jrnieder@gmail.com>,
"git@vger.kernel.org" <git@vger.kernel.org>,
kyle@kyleam.com
Subject: Re: Q: rational for $XDG_CONFIG_HOME/git/config to be "non global" or just a bug?
Date: Mon, 18 Dec 2017 09:21:00 -0500 [thread overview]
Message-ID: <20171218142100.3mhshemnooc3sykv@hopa.kiewit.dartmouth.edu> (raw)
In-Reply-To: <20171218064042.GA25733@sigill.intra.peff.net>
On Mon, 18 Dec 2017, Jeff King wrote:
> To complete that abstraction it seems like reading via "--global" should
> read from both (in the same precedence order that normal config lookup
> uses).
FWIW +1 from me on that ;)
--
Yaroslav O. Halchenko
Center for Open Neuroscience http://centerforopenneuroscience.org
Dartmouth College, 419 Moore Hall, Hinman Box 6207, Hanover, NH 03755
Phone: +1 (603) 646-9834 Fax: +1 (603) 646-1419
WWW: http://www.linkedin.com/in/yarik
next prev parent reply other threads:[~2017-12-18 14:21 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-11 21:11 Q: rational for $XDG_CONFIG_HOME/git/config to be "non global" or just a bug? Yaroslav Halchenko
2017-12-11 22:56 ` Jonathan Nieder
2017-12-12 0:48 ` Yaroslav Halchenko
2017-12-12 1:05 ` Junio C Hamano
2017-12-12 9:36 ` Jacob Keller
2017-12-12 19:36 ` Junio C Hamano
2017-12-13 5:35 ` Jacob Keller
2017-12-12 14:13 ` Yaroslav Halchenko
2017-12-13 5:35 ` Jacob Keller
2017-12-16 22:01 ` brian m. carlson
2017-12-18 4:03 ` Jacob Keller
2017-12-18 6:40 ` Jeff King
2017-12-18 14:21 ` Yaroslav Halchenko [this message]
2017-12-18 16:55 ` Junio C Hamano
2017-12-18 19:56 ` Jacob Keller
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20171218142100.3mhshemnooc3sykv@hopa.kiewit.dartmouth.edu \
--to=yoh@onerussian.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=jacob.keller@gmail.com \
--cc=jrnieder@gmail.com \
--cc=kyle@kyleam.com \
--cc=peff@peff.net \
--cc=sandals@crustytoothpaste.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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).