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

Re: [PATCH v2 2/2] for-each-repo: work correctly in a worktree

From
Junio C Hamano <gitster@pobox.com>
Date
Feb 24, 2026, 21:47 UTC
Message-ID
<xmqqv7flervq.fsf@gitster.g>
In-Reply-To
<4e3f4aa6cd36f779c6c1d6b4f30bb68ed807b9da.1771968924.git.gitgitgadget@gmail.com>
"Derrick Stolee via GitGitGadget" <gitgitgadget@gmail.com> writes:
Show 45 quoted lines
>  static int run_command_on_repo(const char *path, int argc, const char ** argv)
>  {
> -	int i;
> +	int res;
>  	struct child_process child = CHILD_PROCESS_INIT;
> +	char **envvars;
> +	size_t envvar_nr = 0;
>  	char *abspath = interpolate_path(path, 0);
>  
> +	while (local_repo_env[envvar_nr])
> +		envvar_nr++;
> +
> +	CALLOC_ARRAY(envvars, envvar_nr);
> +
> +	for (size_t i = 0; i < envvar_nr; i++) {
> +		envvars[i] = getenv(local_repo_env[i]);
> +
> +		if (envvars[i]) {
> +			unsetenv(local_repo_env[i]);
> +			envvars[i] = xstrdup(envvars[i]);
> +		}
> +	}
>
>  	child.git_cmd = 1;
>  	strvec_pushl(&child.args, "-C", abspath, NULL);
>  
> -	for (i = 0; i < argc; i++)
> +	for (int i = 0; i < argc; i++)
>  		strvec_push(&child.args, argv[i]);
>  
>  	free(abspath);
>  
> -	return run_command(&child);
> +	res = run_command(&child);
> +
> +	for (size_t i = 0; i < envvar_nr; i++) {
> +		if (envvars[i]) {
> +			setenv(local_repo_env[i], envvars[i], 1);
> +			free(envvars[i]);
> +		}
> +	}
> +
> +	free(envvars);
> +	return res;
>  }
  

Doesn't run_command() let you unsetenv in the child without affecting the parent process?

Looking at run-command.c:prep_childenv(), it seems that you can pass "VAR=VAL" to "export VAR=VAL" in the child, and pass "VAR" to "unset VAR" in the child.

Or is it essential to unset in both parent and child while the child is working and that is why we unset in the parent and then restore later? I find this highly confusing.

Show 33 quoted lines
>  int cmd_for_each_repo(int argc,
> diff --git a/t/t0068-for-each-repo.sh b/t/t0068-for-each-repo.sh
> index 512af34c82..d55557a934 100755
> --- a/t/t0068-for-each-repo.sh
> +++ b/t/t0068-for-each-repo.sh
> @@ -10,7 +10,7 @@ TEST_NO_CREATE_REPO=1
>  test_expect_success 'run based on configured value' '
>  	git init one &&
>  	git init two &&
> -	git init three &&
> +	git -C two worktree add --orphan ../three &&
>  	git init ~/four &&
>  	git -C two commit --allow-empty -m "DID NOT RUN" &&
>  	git config --global run.key "$TRASH_DIRECTORY/one" &&
> @@ -35,7 +35,17 @@ test_expect_success 'run based on configured value' '
>  	git -C three log -1 --pretty=format:%s >message &&
>  	grep again message &&
>  	git -C ~/four log -1 --pretty=format:%s >message &&
> -	grep again message
> +	grep again message &&
> +
> +	git -C three for-each-repo --config=run.key -- commit --allow-empty -m "ran from worktree" &&
> +	git -C one log -1 --pretty=format:%s >message &&
> +	grep worktree message &&
> +	git -C two log -1 --pretty=format:%s >message &&
> +	! grep worktree message &&
> +	git -C three log -1 --pretty=format:%s >message &&
> +	grep worktree message &&
> +	git -C ~/four log -1 --pretty=format:%s >message &&
> +	grep worktree message
>  '
>  
>  test_expect_success 'do nothing on empty config' '
Previous: Derrick Stolee via GitGitGadgetNext: Derrick Stolee
Message 14 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. Patrick SteinhardtFeb 24, 2026
  4. Derrick StoleeFeb 24, 2026
  5. 2/2 for-each-repo: work correctly in a worktreeDerrick Stolee via GitGitGadget, Feb 24, 2026
  6. Eric SunshineFeb 24, 2026
  7. Jeff KingFeb 24, 2026
  8. Derrick StoleeFeb 24, 2026
  9. Jeff KingFeb 25, 2026
  10. Patrick SteinhardtFeb 24, 2026
  11. 0/2 for-each-repo: work correctly in a worktreeDerrick Stolee via GitGitGadget, Feb 24, 2026
  12. 1/2 for-each-repo: test outside of repo contextDerrick Stolee via GitGitGadget, Feb 24, 2026
  13. 2/2 for-each-repo: work correctly in a worktreeDerrick Stolee via GitGitGadget, Feb 24, 2026
  14. Junio C HamanoFeb 24, 2026
  15. Derrick StoleeFeb 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. Jeff KingMar 2, 2026
  26. 0/4 for-each-repo: work correctly in a worktreeDerrick Stolee via GitGitGadget, Mar 2, 2026
  27. 1/4 for-each-repo: test outside of repo contextDerrick Stolee via GitGitGadget, Mar 2, 2026
  28. Jeff KingMar 2, 2026
  29. Junio C HamanoMar 2, 2026
  30. Derrick StoleeMar 2, 2026
  31. 2/4 run-command: extract clear_local_repo_env helperDerrick Stolee via GitGitGadget, Mar 2, 2026
  32. Jeff KingMar 2, 2026
  33. Junio C HamanoMar 2, 2026
  34. Derrick StoleeMar 2, 2026
  35. 3/4 for-each-repo: work correctly in a worktreeDerrick Stolee via GitGitGadget, Mar 2, 2026
  36. Jeff KingMar 2, 2026
  37. Derrick StoleeMar 2, 2026
  38. Junio C HamanoMar 2, 2026
  39. 4/4 for-each-repo: simplify passing of parametersDerrick Stolee via GitGitGadget, Mar 2, 2026
  40. Jeff KingMar 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.