[PATCH v2 09/20] config: expose `repo_config_clear()`
- From
Patrick Steinhardt <ps@pks.im>
- Date
- Aug 13, 2024, 09:13 UTC
- Message-ID
- <5e73ef6cec809a3f1009d302b8721b56b048898d.1723540226.git.ps@pks.im>
- In-Reply-To
- <cover.1723540226.git.ps@pks.im>
While we already have `repo_config_clear()` as an alternative to `git_config_clear()` that doesn't rely on `the_repository`, it is not exposed to callers outside of the config subsystem. Do so.
Signed-off-by: Patrick Steinhardt <ps@pks.im> --- config.c | 2 +- config.h | 1 + 2 files changed, 2 insertions(+), 1 deletion(-)
diff --git a/config.c b/config.c index ac89b708e7..476cd73c9e 100644 --- a/config.c +++ b/config.c @@ -2564,7 +2564,7 @@ static void git_config_check_init(struct repository *repo) repo_read_config(repo); } -static void repo_config_clear(struct repository *repo) +void repo_config_clear(struct repository *repo) { if (!repo->config || !repo->config->hash_initialized) return; diff --git a/config.h b/config.h index b13e1bfb8d..8eb3efa0c4 100644 --- a/config.h +++ b/config.h @@ -651,6 +651,7 @@ int git_config_get_string_multi(const char *key, * Resets and invalidates the config cache. */ void git_config_clear(void); +void repo_config_clear(struct repository *repo); /** * Allocates and copies the retrieved string into the `dest` parameter for
-- 2.46.0.46.g406f326d27.dirty