aboutsummaryrefslogtreecommitdiffstats
path: root/fetch-pack.c
diff options
context:
space:
mode:
authorJunio C Hamano <gitster@pobox.com>2025-11-20 11:45:35 -0800
committerJunio C Hamano <gitster@pobox.com>2025-11-24 17:00:47 -0800
commit0bd16856ffb3968de73699ad0555d1fae6c45406 (patch)
tree9d2c78d62c1e4588bd54ae78a59205747af6500c /fetch-pack.c
parentce1a5a22a5beefac8a52da518855b5aecc562874 (diff)
downloadgit-0bd16856ffb3968de73699ad0555d1fae6c45406.tar.gz
config: really treat missing optional path as not configured
These callers expect that git_config_pathname() that returns 0 is a signal that the variable they passed has a string they need to act on. But with the introduction of ":(optional)path" earlier, that is no longer the case. If the path specified by the configuration variable is missing, their variable will get a NULL in it, and they need to act on it (often, just refraining from copying it elsewhere). Signed-off-by: Junio C Hamano <gitster@pobox.com>
Diffstat (limited to 'fetch-pack.c')
-rw-r--r--fetch-pack.c5
1 files changed, 3 insertions, 2 deletions
diff --git a/fetch-pack.c b/fetch-pack.c
index 46c39f85c4..33a3f20bfc 100644
--- a/fetch-pack.c
+++ b/fetch-pack.c
@@ -1872,8 +1872,9 @@ int fetch_pack_fsck_config(const char *var, const char *value,
if (git_config_pathname(&path, var, value))
return -1;
- strbuf_addf(msg_types, "%cskiplist=%s",
- msg_types->len ? ',' : '=', path);
+ if (path)
+ strbuf_addf(msg_types, "%cskiplist=%s",
+ msg_types->len ? ',' : '=', path);
free(path);
return 0;
}