From: Madhu <enometh@meer.net>
To: Matthieu.Moy@grenoble-inp.fr
Cc: Huynh-Khoi-Nguyen.Nguyen@ensimag.imag.fr
Subject: Re: git/path.c - order of accessing ~/.gitconfig
Date: Wed, 18 Sep 2013 23:26:45 +0530 (IST) [thread overview]
Message-ID: <20130918.232645.170158661.enometh@meer.net> (raw)
In-Reply-To: <vpq8uyuxjfe.fsf@anie.imag.fr>
[I posted this via gmane (m3mwnac9ob.fsf@leonis4.robolove.meer.net)
but the posting hasn't appeared, so I'm sending this by email..]
* Matthieu Moy <vpq8uyuxjfe.fsf@anie.imag.fr> :
Wrote on Wed, 18 Sep 2013 17:01:57 +0200:
|> * commit 21cf32279120799a766d22416be7d82d9ecfbd04
|> | In the order of reading, this file comes between the global
|> | configuration file (typically $HOME/.gitconfig) and the system wide
|> | configuration file (typically /etc/gitconfig).
|>
|> However git/config.c (git_config_early) commit accesses xdg_config
|> before user_config. So the comments and documentation are
|> inconsistent with the code.
|
| It seems the commit message is wrong, indeed. But it's too late to fix
| it. OTOH, the documentation seems right to me
| (Documentation/git-config.txt). It says:
No, The commit message is also right. xdg_config indeed comes betweeen
git_etc_gitconfig and user_config, as the commit says, I misunderstood
what the commit was saying because it says this in the reverse order.
Sorry, (nothing to see here) ---Madhu
prev parent reply other threads:[~2013-09-18 18:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-18 14:40 git/path.c - order of accessing ~/.gitconfig Madhu
2013-09-18 15:01 ` Matthieu Moy
2013-09-18 17:56 ` Madhu [this message]
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=20130918.232645.170158661.enometh@meer.net \
--to=enometh@meer.net \
--cc=Huynh-Khoi-Nguyen.Nguyen@ensimag.imag.fr \
--cc=Matthieu.Moy@grenoble-inp.fr \
/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).