From: Derrick Stolee <stolee@gmail.com>
To: Junio C Hamano <gitster@pobox.com>, git@vger.kernel.org
Subject: Re: What's cooking in git.git (Mar 2026, #01)
Date: Tue, 3 Mar 2026 13:10:54 -0500 [thread overview]
Message-ID: <5526480d-ae9e-45e4-b8d2-c853e01af296@gmail.com> (raw)
In-Reply-To: <xmqqbjh5fvsn.fsf@gitster.g>
On 3/2/2026 10:15 PM, Junio C Hamano wrote:
> * ds/for-each-repo-w-worktree (2026-03-02) 4 commits
> - for-each-repo: simplify passing of parameters
> - for-each-repo: work correctly in a worktree
> - run-command: extract clear_local_repo_env helper
> - for-each-repo: test outside of repo context
>
> "git for-each-repo" started from a secondary worktree did not work
> as expected, which has been corrected.
>
> Will merge to 'next'?
> source: <pull.2056.v3.git.1772465805.gitgitgadget@gmail.com>
I just posted v4 with some final polish [1].
[1] https://lore.kernel.org/git/pull.2056.v4.git.1772559114.gitgitgadget@gmail.com/
Thanks,
-Stolee
next prev parent reply other threads:[~2026-03-03 18:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-03 3:15 What's cooking in git.git (Mar 2026, #01) Junio C Hamano
2026-03-03 18:10 ` Derrick Stolee [this message]
2026-03-03 18:43 ` Junio C Hamano
2026-03-04 0:13 ` brian m. carlson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5526480d-ae9e-45e4-b8d2-c853e01af296@gmail.com \
--to=stolee@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.