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>
This commit is contained in:
Junio C Hamano
2025-11-20 11:45:35 -08:00
parent ce1a5a22a5
commit 0bd16856ff
6 changed files with 25 additions and 12 deletions

View File

@@ -1248,7 +1248,7 @@ static int safe_directory_cb(const char *key, const char *value,
} else {
char *allowed = NULL;
if (!git_config_pathname(&allowed, key, value)) {
if (!git_config_pathname(&allowed, key, value) && allowed) {
char *normalized = NULL;
/*