vd/sparse-reset (Was: Re: What's cooking in git.git (Nov 2021, #05; Fri, 19))

From: Elijah Newren <newren@gmail.com>
Date: Nov 20, 2021, 22:20 UTC
Message-ID: <CABPp-BEM4OoAG+WvAyaWyF21a6FOUy=wb=1mt8OVFb_eGEmCLw@mail.gmail.com>
In-Reply-To: <xmqqa6hznvz1.fsf@gitster.g>

Hi,

On Fri, Nov 19, 2021 at 11:53 PM Junio C Hamano <gitster@pobox.com> wrote:

Show 16 quoted lines

>
> * vd/sparse-reset (2021-10-27) 8 commits
>  - unpack-trees: improve performance of next_cache_entry
>  - reset: make --mixed sparse-aware
>  - reset: make sparse-aware (except --mixed)
>  - reset: integrate with sparse index
>  - reset: expand test coverage for sparse checkouts
>  - sparse-index: update command for expand/collapse test
>  - reset: preserve skip-worktree bit in mixed reset
>  - reset: rename is_missing to !is_in_reset_tree
>  (this branch is used by ds/fetch-pull-with-sparse-index and ld/sparse-diff-blame.)
>
>  Various operating modes of "git reset" have been made to work
>  better with the sparse index.
>
>  Will merge to 'next'?

The series looks very good, and is quite close to ready and maybe close enough...but I did spot a tiny commit message issue and had two questions on patch 7. (Sadly, I ineptly put one of those questions as a response to v3[1], while the other question was correctly a response to v5[2].)

Again, my apologies for the late review and not being around to look earlier.

[1] https://lore.kernel.org/git/CABPp-BEcWutcLJWJvO-DC5B59EO4focgCJG1OWYg080j8ti44Q@mail.gmail.com/ [2] https://lore.kernel.org/git/CABPp-BH9qXZObVkEyuLOzoOvw_uPfC_n9QSR=by2+-GVgAGgSw@mail.gmail.com/