From: Junio C Hamano <gitster@pobox.com>
To: Glen Choo <chooglen@google.com>
Cc: git@vger.kernel.org, Atharva Raykar <raykar.ath@gmail.com>,
Emily Shaffer <emilyshaffer@google.com>
Subject: Re: ar/submodule-update (was Re: What's cooking in git.git (Jan 2022, #04; Fri, 14))
Date: Tue, 18 Jan 2022 16:53:03 -0800 [thread overview]
Message-ID: <xmqqczkopmvk.fsf@gitster.g> (raw)
In-Reply-To: kl6llezcy2yr.fsf@chooglen-macbookpro.roam.corp.google.com
Glen Choo <chooglen@google.com> writes:
> Junio C Hamano <gitster@pobox.com> writes:
>
>> * ar/submodule-update (2021-10-13) 9 commits
>> . submodule--helper: rename helper functions
>> . submodule--helper: remove unused helpers
>> . submodule: move core cmd_update() logic to C
>> . submodule--helper: run update using child process struct
>> . submodule--helper: allow setting superprefix for init_submodule()
>> . submodule--helper: refactor get_submodule_displaypath()
>> . submodule--helper: rename helpers for update-clone
>> . submodule--helper: get remote names from any repository
>> . submodule--helper: split up ensure_core_worktree()
>>
>> Rewrite of "git submodule update" in C.
>>
>> Expecting a reroll?
>> cf. <YWiXL+plA7GHfuVv@google.com>
>> source: <20211013051805.45662-10-raykar.ath@gmail.com>
>
> How close are we to getting this into 'next'? Last I checked, it seemed
> like the only remaining piece is to rebase this onto
> es/superproject-aware-submodules.
Unless we have a new version of, a new review or a new ack on any
topic since we tagged -rc0, there should be anything to make them
any closer to 'next'.
In any case, a rebased version would not come from me, so I think
the message I am responding to has To: and Cc: addresses mixed up.
next prev parent reply other threads:[~2022-01-19 0:53 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-15 4:37 What's cooking in git.git (Jan 2022, #04; Fri, 14) Junio C Hamano
2022-01-16 4:25 ` Elijah Newren
2022-01-17 18:30 ` Junio C Hamano
2022-01-18 15:56 ` ab/grep-patterntype (was: What's cooking in git.git (Jan 2022, #04; Fri, 14)) Ævar Arnfjörð Bjarmason
2022-01-18 15:59 ` ab/config-based-hooks-2 " Ævar Arnfjörð Bjarmason
2022-01-18 19:49 ` Glen Choo
2022-01-19 21:32 ` Emily Shaffer
2022-01-18 20:26 ` ab/config-based-hooks-2 Junio C Hamano
2022-01-18 16:08 ` ds/sparse-checkout-requires-per-worktree-config (was Re: What's cooking in git.git (Jan 2022, #04; Fri, 14)) Derrick Stolee
2022-01-18 20:27 ` Junio C Hamano
2022-01-19 0:38 ` ar/submodule-update " Glen Choo
2022-01-19 0:53 ` Junio C Hamano [this message]
2022-01-19 20:06 ` What's cooking in git.git (Jan 2022, #04; Fri, 14) Phillip Wood
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=xmqqczkopmvk.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=chooglen@google.com \
--cc=emilyshaffer@google.com \
--cc=git@vger.kernel.org \
--cc=raykar.ath@gmail.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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).