From: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: ab/env-array (was: What's cooking in git.git (Jun 2022, #01; Wed, 1))
Date: Thu, 02 Jun 2022 14:13:31 +0200 [thread overview]
Message-ID: <220602.86a6avz2hk.gmgdl@evledraar.gmail.com> (raw)
In-Reply-To: <xmqqee07q3xc.fsf@gitster.g>
On Wed, Jun 01 2022, Junio C Hamano wrote:
> * ab/env-array (2022-05-20) 4 commits
> - run-command API users: use "env" not "env_array" in comments & names
> - cocci: remove env_array -> env migration
> - run-command API: rename "env_array" to "env"
> - cocci: add a rename of "struct child_process"'s "env_array" to "env"
>
> Rename .env_array member to .env in the child_process structure.
>
> Expecting a (hopefully final) reroll, before merging it to 'next'.
> cf. <xmqqilq0jhk2.fsf@gitster.g>
> source: <cover-v2-0.4-00000000000-20220520T072122Z-avarab@gmail.com>
I think it should be ready with the v3 I sent today:
https://lore.kernel.org/git/cover-v3-0.2-00000000000-20220602T090745Z-avarab@gmail.com/
next prev parent reply other threads:[~2022-06-02 12:14 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-02 0:55 What's cooking in git.git (Jun 2022, #01; Wed, 1) Junio C Hamano
2022-06-02 1:16 ` gc/zero-length-branch-config-fix (was Re: What's cooking in git.git (Jun 2022, #01; Wed, 1)) Glen Choo
2022-06-02 8:37 ` Ævar Arnfjörð Bjarmason
2022-06-02 12:13 ` Ævar Arnfjörð Bjarmason [this message]
2022-06-02 12:25 ` What's cooking in git.git (Jun 2022, #01; Wed, 1) Derrick Stolee
2022-06-02 14:07 ` Jeff Hostetler
2022-06-02 14:46 ` ab/bug-if-bug (was: What's cooking in git.git (Jun 2022, #01; Wed, 1)) Ævar Arnfjörð Bjarmason
2022-06-02 14:47 ` ab/hooks-regression-fix " Ævar Arnfjörð Bjarmason
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=220602.86a6avz2hk.gmgdl@evledraar.gmail.com \
--to=avarab@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).