Re: Q: rational for $XDG_CONFIG_HOME/git/config to be "non global" or just a bug?
- From
Junio C Hamano <gitster@pobox.com>
- Date
- Dec 12, 2017, 19:36 UTC
- Message-ID
- <xmqqshcf20y1.fsf@gitster.mtv.corp.google.com>
- In-Reply-To
- <CA+P7+xpH6M-FqRJcvsbv=mjj1T04GR6pxz-4NkTmGZUgUKU6wQ@mail.gmail.com>
Jacob Keller <jacob.keller@gmail.com> writes:
Show 14 quoted lines
>> 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. > > It appears that we actually prefer ~/.gitconfig rather than XDG_CONFIG_HOME.. > > And at least based on current cursory testing on the command line, we > do both read and write to the proper location, assuming that > ~/.gitconfig is preferred over $XDG_CONFIG_HOME.
OK, so I misremembered the details but it seems that the behaviour is consistent and there is no ambiguity?
Am I reading you correctly?