git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [PATCH v2] Make 'trust_executable_bit' repository-scoped

From
Junio C Hamano <gitster@pobox.com>
Date
Mar 9, 2026, 15:07 UTC
Message-ID
<xmqq1pht6nyx.fsf@gitster.g>
In-Reply-To
<6e3d373f2f41232ca9015c39ae0ea67d@purelymail.com>
cat@malon.dev writes:
>> Hi drona,
>> 
>> Thanks for the update! Just a quick heads-up: it looks like
>> you forgot to CC Junio (gitster@pobox.com) on this iteration.

No strong need to Cc the maintainer when the patch is not ready to be applied, even though it may be nice. I'll be seeing it either way as I rarely look at my mailbox and use the mailing list archive at lore.kernel.org my primary source of Git patches anyway.

There were discussions on pros and cons moving global recipients of configuration values into a dynamically allocated strucrure, which can change when they are parsed and when bad values in them result in warnings, depending on the way the change is done, and excellent pieces of advice have been given by Phillip Wood. If anything, a change like this should ask for input from him.

>> Additionally, I think it's a good practice to respond to
>> reviews before sending new patches.
Absolutely.
Show 22 quoted lines
>>>  	if (!strcmp(var, "core.filemode")) {
>>> +		prepare_repo_settings(the_repository);
>>>  		the_repository->settings.trust_executable_bit = 
>>> git_config_bool(var, value);
>>>  		return 0;
>>>  	}
>> 
>> Regarding the code, calling 'prepare_repo_settings()' inside
>> 'git_default_core_config()' defeats the purpose of lazy-loading,
>> doesn't it?
>> 
>> if (!strcmp(var, "core.filemode")) {
>> 	prepare_repo_settings(the_repository);
>> 	the_repository->settings.trust_executable_bit = git_config_bool(var, 
>> value);
>> 	return 0;
>> }
>> 
>> I think the standard practice is to drop the variable from
>> 'environment.c' completely and read it directly inside
>> 'repo-settings.c: prepare_repo_settings()' using
>> 'repo_config_get_bool()'.

This "v2" applies to a mythical codebase where trust_executable_bit is somehow a member in the settings structure, which I do not think we have.

Previous: Junio C HamanoNext: Dronaraj Gyawali
Message 10 of 11 in “Refactor 'trust_executable_bit' to repository-scoped setting”
  1. Refactor 'trust_executable_bit' to repository-scoped settingdrona, Mar 1, 2026
  2. Tian YuchenMar 6, 2026
  3. Make 'trust_executable_bit' repository-scopeddrona, Mar 8, 2026
  4. [PATCH v2] Make 'trust_executable_bit' repository-scopeddrona, Mar 8, 2026
  5. Make 'trust_executable_bit' repository-scopeddrona, Mar 8, 2026
  6. cat@malon.devMar 9, 2026
  7. Dronaraj GyawaliMar 9, 2026
  8. Tian YuchenMar 9, 2026
  9. Junio C HamanoMar 9, 2026
  10. Junio C HamanoMar 9, 2026
  11. Dronaraj GyawaliMar 9, 2026

Read the whole thread, see it on lore, or plain text.

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