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

Re: [PATCH 1/2] for-each-repo: stop using the_repository

From
Derrick Stolee <stolee@gmail.com>
Date
Feb 24, 2026, 12:07 UTC
Message-ID
<614c8072-347a-4ba5-8796-4742868389d3@gmail.com>
In-Reply-To
<aZ1s7tONvd9wiYZV@pks.im>
On 2/24/26 4:18 AM, Patrick Steinhardt wrote:
Show 33 quoted lines
> On Tue, Feb 24, 2026 at 03:32:29AM +0000, Derrick Stolee via GitGitGadget wrote:
>> diff --git a/builtin/for-each-repo.c b/builtin/for-each-repo.c
>> index 325a7925f1..478ccf1287 100644
>> --- a/builtin/for-each-repo.c
>> +++ b/builtin/for-each-repo.c
>> @@ -1,5 +1,3 @@
>> -#define USE_THE_REPOSITORY_VARIABLE
>> -
>>   #include "builtin.h"
>>   #include "config.h"
>>   #include "gettext.h"
>> @@ -33,7 +31,7 @@ static int run_command_on_repo(const char *path, int argc, const char ** argv)
>>   int cmd_for_each_repo(int argc,
>>   		      const char **argv,
>>   		      const char *prefix,
>> -		      struct repository *repo UNUSED)
>> +		      struct repository *repo)
>>   {
>>   	static const char *config_key = NULL;
>>   	int keep_going = 0;
>> @@ -55,7 +53,7 @@ int cmd_for_each_repo(int argc,
>>   	if (!config_key)
>>   		die(_("missing --config=<config>"));
>>   
>> -	err = repo_config_get_string_multi(the_repository, config_key, &values);
>> +	err = repo_config_get_string_multi(repo, config_key, &values);
>>   	if (err < 0)
>>   		usage_msg_optf(_("got bad config --config=%s"),
>>   			       for_each_repo_usage, options, config_key);
> 
> The command is marked as `RUN_SETUP_GENTLY`, so it may run in a context
> where there is no repository. In such cases, `repo` would be `NULL`, and
> that would cause the command to segfault here, wouldn't it?
Ah. That's an interesting subtlety of the setup that I did not know.

I'll make sure this is covered in tests, because the current tests run in the default test repo but our expected use case should be outside a repo.

Thanks, -Stolee

Previous: Patrick SteinhardtNext: Derrick Stolee
Message 8 of 48 in “for-each-repo: work correctly in a worktree”
  1. 0/2 for-each-repo: work correctly in a worktreeDerrick Stolee via GitGitGadget, Feb 24, 2026
  2. 1/2 for-each-repo: stop using the_repositoryDerrick Stolee via GitGitGadget, Feb 24, 2026
  3. 2/2 for-each-repo: work correctly in a worktreeDerrick Stolee via GitGitGadget, Feb 24, 2026
  4. Eric SunshineFeb 24, 2026
  5. Jeff KingFeb 24, 2026
  6. Patrick SteinhardtFeb 24, 2026
  7. Patrick SteinhardtFeb 24, 2026
  8. Derrick StoleeFeb 24, 2026
  9. Derrick StoleeFeb 24, 2026
  10. 0/2 for-each-repo: work correctly in a worktreeDerrick Stolee via GitGitGadget, Feb 24, 2026
  11. 1/2 for-each-repo: test outside of repo contextDerrick Stolee via GitGitGadget, Feb 24, 2026
  12. 2/2 for-each-repo: work correctly in a worktreeDerrick Stolee via GitGitGadget, Feb 24, 2026
  13. Junio C HamanoFeb 24, 2026
  14. Derrick StoleeFeb 25, 2026
  15. Jeff KingFeb 25, 2026
  16. Jeff KingFeb 25, 2026
  17. Derrick StoleeFeb 26, 2026
  18. Junio C HamanoFeb 26, 2026
  19. Phillip WoodFeb 26, 2026
  20. Junio C HamanoFeb 27, 2026
  21. Derrick StoleeFeb 27, 2026
  22. Jeff KingFeb 27, 2026
  23. Jeff KingFeb 27, 2026
  24. Derrick StoleeMar 2, 2026
  25. 0/4 for-each-repo: work correctly in a worktreeDerrick Stolee via GitGitGadget, Mar 2, 2026
  26. 1/4 for-each-repo: test outside of repo contextDerrick Stolee via GitGitGadget, Mar 2, 2026
  27. 2/4 run-command: extract clear_local_repo_env helperDerrick Stolee via GitGitGadget, Mar 2, 2026
  28. 3/4 for-each-repo: work correctly in a worktreeDerrick Stolee via GitGitGadget, Mar 2, 2026
  29. 4/4 for-each-repo: simplify passing of parametersDerrick Stolee via GitGitGadget, Mar 2, 2026
  30. Jeff KingMar 2, 2026
  31. Jeff KingMar 2, 2026
  32. Jeff KingMar 2, 2026
  33. Jeff KingMar 2, 2026
  34. Jeff KingMar 2, 2026
  35. Junio C HamanoMar 2, 2026
  36. Junio C HamanoMar 2, 2026
  37. Derrick StoleeMar 2, 2026
  38. Derrick StoleeMar 2, 2026
  39. Derrick StoleeMar 2, 2026
  40. Junio C HamanoMar 2, 2026
  41. 0/4 for-each-repo: work correctly in a worktreeDerrick Stolee via GitGitGadget, Mar 3, 2026
  42. 1/4 for-each-repo: test outside of repo contextDerrick Stolee via GitGitGadget, Mar 3, 2026
  43. 2/4 run-command: extract sanitize_repo_env helperDerrick Stolee via GitGitGadget, Mar 3, 2026
  44. 3/4 for-each-repo: work correctly in a worktreeDerrick Stolee via GitGitGadget, Mar 3, 2026
  45. 4/4 for-each-repo: simplify passing of parametersDerrick Stolee via GitGitGadget, Mar 3, 2026
  46. Jeff KingMar 5, 2026
  47. Patrick SteinhardtMar 5, 2026
  48. Derrick StoleeMar 5, 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.