git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: 0xAX <kuleshovmail@gmail.com>
To: "git@vger.kernel.org" <git@vger.kernel.org>
Cc: 0xAX <kuleshovmail@gmail.com>, Alex Kuleshov <kuleshovmail@gmial.com>
Subject: [PATCH 1/1] git-config: git-config --list fixed when GIT_CONFIG value starts with ~/
Date: Sat, 15 Nov 2014 00:29:20 +0600	[thread overview]
Message-ID: <1415989760-20259-1-git-send-email-kuleshovmail@gmail.com> (raw)

When we execute git config --list and $GIT_CONFIG value starts with home
prefix - ~/ it produces folowing error - fatal: unable to read config
file '~/.gitconfig': No such file or directory. This patch fixed it with
expand_user_path for configuration file path before git-config --list
call.

Signed-off-by: Alex Kuleshov <kuleshovmail@gmial.com>
Signed-off-by: 0xAX <kuleshovmail@gmail.com>
---
 builtin/config.c | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/builtin/config.c b/builtin/config.c
index 7bba516..df1bee0 100644
--- a/builtin/config.c
+++ b/builtin/config.c
@@ -540,6 +540,8 @@ int cmd_config(int argc, const char **argv, const char *prefix)
 
 	if (actions == ACTION_LIST) {
 		check_argc(argc, 0, 0);
+		const char* newpath = expand_user_path(given_config_source.file);
+		given_config_source.file = newpath;
 		if (git_config_with_options(show_all_config, NULL,
 					    &given_config_source,
 					    respect_includes) < 0) {
-- 
2.1.3.17.g7fa1365.dirty

             reply	other threads:[~2014-11-14 18:29 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-14 18:29 0xAX [this message]
2014-11-14 19:19 ` [PATCH 1/1] git-config: git-config --list fixed when GIT_CONFIG value starts with ~/ Eric Sunshine
2014-11-14 19:30   ` Jeff King
2014-11-14 19:38     ` Alex Kuleshov
2014-11-14 20:04       ` Jeff King
2014-11-14 20:10 ` Junio C Hamano

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=1415989760-20259-1-git-send-email-kuleshovmail@gmail.com \
    --to=kuleshovmail@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=kuleshovmail@gmial.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.
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).