Re: What's cooking in git.git (Jul 2025, #06; Tue, 22)

> On Tue, Jul 22, 2025 at 05:11:35PM -0700, Junio C Hamano wrote:
>> * ps/config-wo-the-repository (2025-07-17) 22 commits
>>   - config: fix sign comparison warnings
>>   - config: move Git config parsing into "environment.c"
>>   - config: remove unused `the_repository` wrappers
>>   - config: drop `git_config_set_multivar()` wrapper
>>   - config: drop `git_config_get_multivar_gently()` wrapper
>>   - config: drop `git_config_set_multivar_in_file_gently()` wrapper
>>   - config: drop `git_config_set_in_file_gently()` wrapper
>>   - config: drop `git_config_set()` wrapper
>>   - config: drop `git_config_set_gently()` wrapper
>>   - config: drop `git_config_set_in_file()` wrapper
>>   - config: drop `git_config_get_bool()` wrapper
>>   - config: drop `git_config_get_ulong()` wrapper
>>   - config: drop `git_config_get_int()` wrapper
>>   - config: drop `git_config_get_string()` wrapper
>>   - config: drop `git_config_get_string()` wrapper
>>   - config: drop `git_config_get_string_multi()` wrapper
>>   - config: drop `git_config_get_value()` wrapper
>>   - config: drop `git_config_get_value()` wrapper
>>   - config: drop `git_config_get()` wrapper
>>   - config: drop `git_config_clear()` wrapper
>>   - config: drop `git_config()` wrapper
>>   - Merge branch 'bc/use-sha256-by-default-in-3.0' into ps/config-wo-the-repository
>>
>>   The config API had a set of convenience wrapper functions that
>>   implicitly use the_repository instance; they have been removed and
>>   inlined at the calling sites.
>>
>>   Will merge to 'next'?
>>   source: <20250717-pks-config-wo-the-repository-v1-0-d888e4a17de1@pks.im>
> 
> I think the only commit that really needs review is the last one that
> fixes the sign comparison warnings. As long as people are fine with that
> commit I'm happy to have it merged.