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

Re: [PATCH v4 0/4] for-each-repo: work correctly in a worktree

From
Derrick Stolee <stolee@gmail.com>
Date
Mar 5, 2026, 17:23 UTC
Message-ID
<fee9576a-787c-44f6-8630-cdec29df2b3b@gmail.com>
In-Reply-To
<aakfT3oio1XQSl4R@pks.im>
On 3/5/2026 1:14 AM, Patrick Steinhardt wrote:
Show 16 quoted lines
> On Wed, Mar 04, 2026 at 08:20:35PM -0500, Jeff King wrote:
>> On Tue, Mar 03, 2026 at 05:31:50PM +0000, Derrick Stolee via GitGitGadget wrote:
>>
>>> Updates in V4
>>> =============
>>>
>>> Minor updates from Peff's review:
>>>
>>>  1. Update the comment of prepare_other_repo_env() to avoid duplication.
>>>  2. Rename the new method to sanitize_repo_env().
>>>  3. Move incorrect removal of 'int i;' to correct patch.
>>
>> This looks good to me. Thanks for accommodating my somewhat-bikeshedding
>> review.
> 
> Likewise, this patch series looks good to me. Thanks!

Thanks, all. This was far less trivial than I thought going into it, so the careful review was essential.

Thanks, -Stolee

Previous: Patrick Steinhardt
Message 48 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.