git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Madhu <enometh@meer.net>
To: git@vger.kernel.org
Cc: Huynh Khoi Nguyen Nguyen  <Huynh-Khoi-Nguyen.Nguyen@ensimag.imag.fr>
Subject: git/path.c - order of accessing ~/.gitconfig
Date: Wed, 18 Sep 2013 20:10:06 +0530 (IST)	[thread overview]
Message-ID: <20130918.201006.407922449.enometh@meer.net> (raw)


* commit 21cf32279120799a766d22416be7d82d9ecfbd04
|
| Author: Huynh Khoi Nguyen Nguyen <Huynh-Khoi-Nguyen.Nguyen@ensimag.imag.fr>
| Date:   Fri Jun 22 11:03:23 2012 +0200
|
|    config: read (but not write) from $XDG_CONFIG_HOME/git/config file
|
|    Teach git to read the "gitconfig" information from a new location,
|    $XDG_CONFIG_HOME/git/config; this allows the user to avoid
|    cluttering $HOME with many per-application configuration files.
|
|    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.

[This looks like an intentional bug, I spotted it when commenting out
 the accesses to files under ~/.config.  (protip: chmod 000 ~/.config helps
 identify and blacklist NWO "apps" and now git started complaining) ---Madhu

             reply	other threads:[~2013-09-18 14:40 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-18 14:40 Madhu [this message]
2013-09-18 15:01 ` git/path.c - order of accessing ~/.gitconfig Matthieu Moy
2013-09-18 17:56   ` Madhu

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.201006.407922449.enometh@meer.net \
    --to=enometh@meer.net \
    --cc=Huynh-Khoi-Nguyen.Nguyen@ensimag.imag.fr \
    --cc=git@vger.kernel.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 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).