From: Junio C Hamano <gitster@pobox.com>
To: Jonathan Nieder <jrnieder@gmail.com>
Cc: Yaroslav Halchenko <yoh@onerussian.com>,
"git\@vger.kernel.org" <git@vger.kernel.org>,
kyle@kyleam.com, Jeff King <peff@peff.net>
Subject: Re: Q: rational for $XDG_CONFIG_HOME/git/config to be "non global" or just a bug?
Date: Mon, 11 Dec 2017 17:05:01 -0800 [thread overview]
Message-ID: <xmqqtvww3gea.fsf@gitster.mtv.corp.google.com> (raw)
In-Reply-To: <20171211225615.GC214273@aiede.mtv.corp.google.com> (Jonathan Nieder's message of "Mon, 11 Dec 2017 14:56:15 -0800")
Jonathan Nieder <jrnieder@gmail.com> writes:
> I think the documentation
>
> ~/.gitconfig
> User-specific configuration file. Also called "global"
> configuration file.
>
> should be clarified --- e.g. it could say
>
> $XDG_CONFIG_HOME/git/config
> ~/.gitconfig
> User-specific configuration files. Because options in
> these files are not specific to any repository, thes
> are sometimes called global configuration files.
Yeah, I think that makes sense.
> As for "git config --global", I think the best thing would be to split
> it into two options: something like "git config --user" and "git
> config --xdg-user". That way, it is unambiguous which configuration
> file the user intends to inspect or modify. When a user calls "git
> config --global" and both files exist, it could warn that the command
> is ambiguous.
>
> Thoughts?
I actually thought that the plan was "you either have this, or the
other one, never both at the same time" (and I think those who
pushed the XDG thing in to the system made us favor it over the
traditional one). So as long as --global updates the one that
exists, and updates XDG one when both or neither do, I think we
should be OK. And from that viewpoint, we definitely do not want
two kinds of --global to pretend as if we support use of both at the
same time.
next prev parent reply other threads:[~2017-12-12 1:05 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 [this message]
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
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=xmqqtvww3gea.fsf@gitster.mtv.corp.google.com \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=jrnieder@gmail.com \
--cc=kyle@kyleam.com \
--cc=peff@peff.net \
--cc=yoh@onerussian.com \
/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).