From: Kaartic Sivaraam <kaartic.sivaraam@gmail.com>
To: Atharva Raykar <raykar.ath@gmail.com>
Cc: git@vger.kernel.org, gitscale@google.com,
Junio C Hamano <gitster@pobox.com>,
Emily Shaffer <emilyshaffer@google.com>
Subject: Re: Submodule UX overhaul update (was: What's cooking in git.git (Jan 2022, #07; Mon, 24))
Date: Wed, 26 Jan 2022 20:46:43 +0530 [thread overview]
Message-ID: <8171a321-20a0-508d-f2fe-57707d03a00f@gmail.com> (raw)
In-Reply-To: <YfBTRuPrGGjepe+D@google.com>
On 26/01/22 1:15 am, Emily Shaffer wrote:
> Finally finding the time to write up another "what's cooking as pertain
> to overhauling submodules UX" reply.
>
> On Mon, Jan 24, 2022 at 11:39:58AM -0800, Junio C Hamano wrote:
>> --------------------------------------------------
>> [Stalled]
>>
>> * 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>
>
> Sounds like Glen is interested in this series with regard to some edge
> cases about cloning newly added submodules during a 'git fetch
> --recurse-submodules'. I'm curious to hear from Atharva about the status
> of this work :)
>
Pinging Atharva for this.
--
Sivaraam
next prev parent reply other threads:[~2022-01-26 15:16 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-24 19:39 What's cooking in git.git (Jan 2022, #07; Mon, 24) Junio C Hamano
2022-01-25 19:45 ` Submodule UX overhaul update (was: What's cooking in git.git (Jan 2022, #07; Mon, 24)) Emily Shaffer
2022-01-26 14:09 ` Ævar Arnfjörð Bjarmason
2022-01-26 17:27 ` Emily Shaffer
2022-01-26 15:16 ` Kaartic Sivaraam [this message]
2022-01-26 16:35 ` Atharva Raykar
2022-01-26 17:43 ` Emily Shaffer
2022-01-26 17:50 ` Glen Choo
2022-01-28 7:40 ` ps/avoid-unnecessary-hook-invocation-with-packed-refs (Was: " Patrick Steinhardt
2022-01-28 21:14 ` ps/avoid-unnecessary-hook-invocation-with-packed-refs Junio C Hamano
2022-01-31 9:50 ` flags types/names (was: ps/avoid-unnecessary-hook-invocation-with-packed-refs) Han-Wen Nienhuys
2022-01-31 17:13 ` flags types/names Junio C Hamano
2022-01-28 22:31 ` What's cooking in git.git (Jan 2022, #07; Mon, 24) brian m. carlson
2022-02-04 0:27 ` Junio C Hamano
2022-02-04 17:27 ` René Scharfe
2022-02-02 11:28 ` ab/auto-detect-zlib-compress2 (was: What's cooking in git.git (Jan 2022, #07; Mon, 24)) Æ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=8171a321-20a0-508d-f2fe-57707d03a00f@gmail.com \
--to=kaartic.sivaraam@gmail.com \
--cc=emilyshaffer@google.com \
--cc=git@vger.kernel.org \
--cc=gitscale@google.com \
--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 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).