Re: [PATCH v3 5/5] setup: allow not marking self owned repos as safe in `ensure_safe_repository()`

From: Junio C Hamano <gitster@pobox.com>
Date: Oct 16, 2025, 19:58 UTC
Message-ID: <xmqqjz0u39g0.fsf@gitster.g>
In-Reply-To: <20251016053322.44495-6-git@lohmann.sh>

Michael Lohmann <git@lohmann.sh> writes:

> Git considers all repositories as safe, if they are either
>  - explicitly set in "safe.directory" config, or
>  - the user owns the repo

If you are going to reroll this step, please add a few more cases to the list above. There are other code paths in setup.c that does not call ensure_valid_ownership(). Treating an explicitly specified git directory as safe is one of them (there may or may not be others, I didn't check).

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