Re: [PATCH v3 0/3] environment: clean up repository config handling

From: Patrick Steinhardt <ps@pks.im>
Date: Aug 7, 2026, 11:04 UTC
Message-ID: <anW7wHfUxYj9cj0P@pks.im>
In-Reply-To: <20260807085932.3958759-1-cat@malon.dev>

On Fri, Aug 07, 2026 at 04:59:29PM +0800, Tian Yuchen wrote:

Show 12 quoted lines

> Hi all,
> 
> This series contains several cleanup patches for repository configuration
> handling.
> 
> No functional changes are intended. The patches make the related code
> more consistent and easier to maintain by improving documentation,
> formatting, and the organization of repo_config_values.
> 
> RFC:
> If there are other small cleanups in this area that would be useful to
> include, suggestions are welcome.

Somewhat unrelated to this patch series, but I was wondering whether you plan to drop the limitation in `repo_config_values()` that requires that the passed-in repository is `the_repository`. This limitation is starting to create problems as more and more of our infrastructure is migrating into `struct repo_config_values`, so using a different repo than `the_repository` is starting to become harder and harder in our codebase.

Thanks!

Patrick