From: Elijah Newren <newren@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: Git Mailing List <git@vger.kernel.org>,
Josh Steadmon <steadmon@google.com>
Subject: js/apply-partial-clone-filters-recursively (Was: Re: What's cooking in git.git (Feb 2022, #04; Tue, 15))
Date: Tue, 15 Feb 2022 21:01:40 -0800 [thread overview]
Message-ID: <CABPp-BG+-ZAX7DcKNc=Z9sXNAJKUEDvrESesJsH91=ze2zLm5A@mail.gmail.com> (raw)
In-Reply-To: <xmqqk0dwyrcv.fsf@gitster.g>
On Tue, Feb 15, 2022 at 12:01 PM Junio C Hamano <gitster@pobox.com> wrote:
>
> * js/apply-partial-clone-filters-recursively (2022-02-09) 1 commit
> - clone, submodule: pass partial clone filters to submodules
>
> "git clone --filter=... --recurse-submodules" only makes the
> top-level a partial clone, while submodules are fully cloned. This
> behaviour is changed to pass the same filter down to the submodules.
>
> Will merge to 'next'?
> source: <690d2316ad518ea4551821b2b3aa652996858475.1644034886.git.steadmon@google.com>
I think so. Sorry for letting it slip through the crack, but v2
addressed all my feedback. Further, v3 was Reviewed-by Jonathan Tan
as well. I think it's ready to merge down.
next prev parent reply other threads:[~2022-02-16 5:02 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-15 17:25 What's cooking in git.git (Feb 2022, #04; Tue, 15) Junio C Hamano
2022-02-15 22:17 ` ja/i18n-common-messages (was: What's cooking in git.git (Feb 2022, #04; Tue, 15)) Ævar Arnfjörð Bjarmason
2022-02-15 22:22 ` ab/ambiguous-object-name & ab/only-single-progress-at-once " Ævar Arnfjörð Bjarmason
2022-02-16 4:52 ` en/present-despite-skipped (Was: " Elijah Newren
2022-02-16 9:44 ` Ævar Arnfjörð Bjarmason
2022-02-16 16:38 ` Elijah Newren
2022-02-16 5:01 ` Elijah Newren [this message]
2022-02-16 5:06 ` ds/sparse-checkout-requires-per-worktree-config " Elijah Newren
2022-02-16 13:54 ` Derrick Stolee
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='CABPp-BG+-ZAX7DcKNc=Z9sXNAJKUEDvrESesJsH91=ze2zLm5A@mail.gmail.com' \
--to=newren@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=steadmon@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.
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).