Junio C Hamano <gitster@xxxxxxxxx> writes: > Glen Choo <chooglen@xxxxxxxxxx> writes: > >> Junio C Hamano <gitster@xxxxxxxxx> writes: >> >>> * gc/submodule-clone-update-with-branches (2022-10-30) 8 commits >>> - clone, submodule update: create and check out branches >>> - submodule--helper: remove update_data.suboid >>> - submodule update: refactor update targets >>> - submodule: return target of submodule symref >>> - t5617: drop references to remote-tracking branches >>> - submodule--helper clone: create named branch >>> - repo-settings: add submodule_propagate_branches >>> - clone: teach --detach option >>> >>> "git clone --recurse-submodules" and "git submodule update" learns >>> to honor the "propagete branches" option. >>> >>> Waiting for review on the updated round. >>> source: <pull.1321.v3.git.git.1666988096.gitgitgadget@xxxxxxxxx> >> >> Jonathan left adequate feedback on the updated round, and we had decided >> on a direction for the reroll in [1]. >> >> However, Calvin is also looking at how we could parallelize worktree >> updates to speed up "git clone --recurse-submodules", so the Google >> folks are taking an even bigger step back to figure out how worktree >> updating should look, which will probably end in a different approach >> from [1], but it should answer the questions on that thread about "git >> checkout" with branches. >> >> [1] https://lore.kernel.org/git/20221123013319.1597025-1-jonathantanmy@xxxxxxxxxx > > Thanks for a status report. > > So it sounds more like "discard for now" to expect a fresh restart. Yes, that is accurate :)
