summaryrefslogtreecommitdiff
path: root/builtin/clone.c
diff options
context:
space:
mode:
authorJunio C Hamano <gitster@pobox.com>2013-02-01 20:39:36 (GMT)
committerJunio C Hamano <gitster@pobox.com>2013-02-01 20:39:37 (GMT)
commitba96aa67be5a85a7f7a61e967c16e38d077fce88 (patch)
treec027aa6786f7d68de6fd8f4d2afa4eeef1145bbd /builtin/clone.c
parent2532d891a4aab003a5ce19f04509fd8549754485 (diff)
parent3f4f4cc0da03b312fabcd5a509baa8092de39534 (diff)
downloadgit-ba96aa67be5a85a7f7a61e967c16e38d077fce88.zip
git-ba96aa67be5a85a7f7a61e967c16e38d077fce88.tar.gz
git-ba96aa67be5a85a7f7a61e967c16e38d077fce88.tar.bz2
Merge branch 'jc/no-git-config-in-clone'
We stopped paying attention to $GIT_CONFIG environment that points at a single configuration file from any command other than "git config" quite a while ago, but "git clone" internally set, exported, and then unexported the variable during its operation unnecessarily. * jc/no-git-config-in-clone: clone: do not export and unexport GIT_CONFIG
Diffstat (limited to 'builtin/clone.c')
-rw-r--r--builtin/clone.c9
1 files changed, 0 insertions, 9 deletions
diff --git a/builtin/clone.c b/builtin/clone.c
index 36ec99d..e0aaf13 100644
--- a/builtin/clone.c
+++ b/builtin/clone.c
@@ -767,8 +767,6 @@ int cmd_clone(int argc, const char **argv, const char *prefix)
atexit(remove_junk);
sigchain_push_common(remove_junk_on_signal);
- setenv(CONFIG_ENVIRONMENT, mkpath("%s/config", git_dir), 1);
-
if (safe_create_leading_directories_const(git_dir) < 0)
die(_("could not create leading directories of '%s'"), git_dir);
@@ -787,13 +785,6 @@ int cmd_clone(int argc, const char **argv, const char *prefix)
init_db(option_template, INIT_DB_QUIET);
write_config(&option_config);
- /*
- * At this point, the config exists, so we do not need the
- * environment variable. We actually need to unset it, too, to
- * re-enable parsing of the global configs.
- */
- unsetenv(CONFIG_ENVIRONMENT);
-
git_config(git_default_config, NULL);
if (option_bare) {