From: Glen Choo <chooglen@google.com>
To: Junio C Hamano <gitster@pobox.com>, git@vger.kernel.org
Cc: Atharva Raykar <raykar.ath@gmail.com>,
Emily Shaffer <emilyshaffer@google.com>
Subject: ar/submodule-update (was Re: What's cooking in git.git (Jan 2022, #04; Fri, 14))
Date: Tue, 18 Jan 2022 16:38:20 -0800 [thread overview]
Message-ID: <kl6llezcy2yr.fsf@chooglen-macbookpro.roam.corp.google.com> (raw)
In-Reply-To: <xmqqy23h4nss.fsf@gitster.g>
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.
I have some planned work that will teach "git fetch" how to clone newly
added submodules (this is the issue described in the BUGS section of
Documentation/git-fetch.txt). That work will probably use the same
machinery as `git submodule update`, so I'm wondering whether it's
better to base this new work off ar/submodule-update or master.
next prev parent reply other threads:[~2022-01-19 0:38 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 ` Glen Choo [this message]
2022-01-19 0:53 ` ar/submodule-update " Junio C Hamano
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=kl6llezcy2yr.fsf@chooglen-macbookpro.roam.corp.google.com \
--to=chooglen@google.com \
--cc=emilyshaffer@google.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--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.
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.