From: Glen Choo <chooglen@google.com>
To: Junio C Hamano <gitster@pobox.com>, git@vger.kernel.org
Subject: gc/recursive-fetch-with-unused-submodules (was Re: What's cooking in git.git (Feb 2022, #05; Thu, 17))
Date: Fri, 18 Feb 2022 10:49:18 +0800 [thread overview]
Message-ID: <kl6lv8xc51ox.fsf@chooglen-macbookpro.roam.corp.google.com> (raw)
In-Reply-To: <xmqqley93rkw.fsf@gitster.g>
Junio C Hamano <gitster@pobox.com> writes:
> * gc/recursive-fetch-with-unused-submodules (2022-02-10) 8 commits
> - submodule: fix bug and remove add_submodule_odb()
> - fetch: fetch unpopulated, changed submodules
> - submodule: extract get_fetch_task()
> - t5526: use grep to assert on fetches
> - t5526: introduce test helper to assert on fetches
> - submodule: make static functions read submodules from commits
> - submodule: store new submodule commits oid_array in a struct
> - submodule: inline submodule_commits() into caller
>
> When "git fetch --recurse-submodules" grabbed submodule commits
> that would be needed to recursively check out newly fetched commits
> in the superproject, it only paid attention to submodules that are
> in the current checkout of the superproject. We now do so for all
> submodules that have been run "git submodule init" on.
>
> Will merge to 'next'?
> source: <20220210044152.78352-1-chooglen@google.com>
I'm working on another version that should hopefully address some
reviewer feedback on v2. I'd prefer to hold off until that version is
reviewed :)
next prev parent reply other threads:[~2022-02-18 2:50 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-18 1:13 What's cooking in git.git (Feb 2022, #05; Thu, 17) Junio C Hamano
2022-02-18 2:49 ` Glen Choo [this message]
2022-02-18 16:51 ` gc/recursive-fetch-with-unused-submodules (was Re: What's cooking in git.git (Feb 2022, #05; Thu, 17)) Junio C Hamano
2022-02-18 3:28 ` What's cooking in git.git (Feb 2022, #05; Thu, 17) Elijah Newren
2022-02-18 16:51 ` Junio C Hamano
2022-02-18 5:19 ` ds/core-untrac[k]ed-cache-config (Was: Re: What's cooking in git.git (Feb 2022, #05; Thu, 17)) Elijah Newren
2022-02-18 16:50 ` ds/core-untrac[k]ed-cache-config Junio C Hamano
2022-02-19 1:53 ` en/present-despite-skipped (Re: What's cooking in git.git (Feb 2022, #05; Thu, 17)) Jonathan Nieder
2022-02-22 23:52 ` Jonathan Nieder
2022-02-23 19:39 ` Junio C Hamano
2022-02-25 16:43 ` Jonathan Nieder
2022-02-21 11:14 ` pw/single-key-interactive (was " 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=kl6lv8xc51ox.fsf@chooglen-macbookpro.roam.corp.google.com \
--to=chooglen@google.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.
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).