All of lore.kernel.org
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Jonathan Tan <jonathantanmy@google.com>
Cc: git@vger.kernel.org
Subject: Re: What's cooking in git.git (Feb 2022, #03; Sat, 12)
Date: Mon, 14 Feb 2022 13:16:11 -0800	[thread overview]
Message-ID: <xmqqv8xh1750.fsf@gitster.g> (raw)
In-Reply-To: <20220214200155.1412357-1-jonathantanmy@google.com> (Jonathan Tan's message of "Mon, 14 Feb 2022 12:01:54 -0800")

Jonathan Tan <jonathantanmy@google.com> writes:

> 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>
>
> This should wait at least until a v2 that addresses comments from both
> of us, I believe.

Indeed.  Thanks.

  reply	other threads:[~2022-02-14 21:16 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-13  9:24 What's cooking in git.git (Feb 2022, #03; Sat, 12) Junio C Hamano
2022-02-14 20:01 ` Jonathan Tan
2022-02-14 21:16   ` Junio C Hamano [this message]
2022-02-15  2:09 ` Chen BoJun
2022-02-15 23:56   ` Junio C Hamano
2022-02-15 16:24 ` js/use-builtin-add-i (was Re: What's cooking in git.git (Feb 2022, #03; Sat, 12)) 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=xmqqv8xh1750.fsf@gitster.g \
    --to=gitster@pobox.com \
    --cc=git@vger.kernel.org \
    --cc=jonathantanmy@google.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.