Re: [PATCH v3 1/8] scalar: constrain enlistment search

From: Derrick Stolee <derrickstolee@github.com>
Date: Aug 19, 2022, 18:32 UTC
Message-ID: <0f2df5ed-3380-8162-80c9-10d2eb644965@github.com>
In-Reply-To: <2f6cad8361324cecdb0ee7b13a96477a8317c358.1660858853.git.gitgitgadget@gmail.com>

On 8/18/2022 5:40 PM, Victoria Dye via GitGitGadget wrote:

Show 5 quoted lines

> From: Victoria Dye <vdye@github.com>
> 
> Make the search for repository and enlistment root in
> 'setup_enlistment_directory()' more constrained to simplify behavior and
> adhere to 'GIT_CEILING_DIRECTORIES'.

Thanks for doing this rather substantial rework. The logic makes sense to me and the tests really help to demonstrate the different cases.

-Stolee

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