Re: [PATCH 1/1] config: allow user to know scope of config options

From: Junio C Hamano <gitster@pobox.com>
Date: Dec 19, 2019, 17:51 UTC
Message-ID: <xmqqy2v8b3w7.fsf@gitster-ct.c.googlers.com>
In-Reply-To: <20191219050545.GC89333@coredump.intra.peff.net>

Jeff King <peff@peff.net> writes:

> ... So if git_config_source grows an enum to select the type, and
> all that filename-resolution gets pushed down into config_with_options(),
> the whole thing would fall out naturally, I think.

Makes sense.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.