Re: [PATCH 6/9] For each exclude pattern, store information about where it came from

From: Junio C Hamano <gitster@pobox.com>
Date: Sep 2, 2012, 19:02 UTC
Message-ID: <7vipbwgnnv.fsf@alter.siamese.dyndns.org>
In-Reply-To: <997D30474124498FBFBA89C2E20F7773@PhilipOakley>

"Philip Oakley" <philipoakley@iee.org> writes:

> Is there a way to identify the config core.excludesfile if present?
> i.e. that it is from that config variable, rather than directory
> traversal.

If the code handles $GIT_DIR/info/exclude then that configuration would also be handled the same way, no?

$ 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.