From: Elijah Newren <newren@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: Git Mailing List <git@vger.kernel.org>, Victoria Dye <vdye@github.com>
Subject: vd/sparse-reset (Was: Re: What's cooking in git.git (Nov 2021, #05; Fri, 19))
Date: Sat, 20 Nov 2021 14:20:15 -0800 [thread overview]
Message-ID: <CABPp-BEM4OoAG+WvAyaWyF21a6FOUy=wb=1mt8OVFb_eGEmCLw@mail.gmail.com> (raw)
In-Reply-To: <xmqqa6hznvz1.fsf@gitster.g>
Hi,
On Fri, Nov 19, 2021 at 11:53 PM Junio C Hamano <gitster@pobox.com> wrote:
>
> * 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/
next prev parent reply other threads:[~2021-11-20 22:20 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-20 7:10 What's cooking in git.git (Nov 2021, #05; Fri, 19) Junio C Hamano
2021-11-20 11:18 ` Fabian Stelzer
2021-11-20 17:30 ` Elijah Newren
2021-11-20 22:20 ` Elijah Newren [this message]
2021-11-21 2:00 ` Elijah Newren
2021-11-22 17:59 ` vd/sparse-sparsity-fix-on-read (Was: Re: What's cooking in git.git (Nov 2021, #05; Fri, 19)) Elijah Newren
2021-11-22 18:00 ` What's cooking in git.git (Nov 2021, #05; Fri, 19) Glen Choo
2021-11-22 18:05 ` Junio C Hamano
2021-11-22 22:36 ` Glen Choo
2021-11-23 13:22 ` ab/mark-leak-free-tests-even-more (was: What's cooking in git.git (Nov 2021, #05; Fri, 19)) Ævar Arnfjörð Bjarmason
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-BEM4OoAG+WvAyaWyF21a6FOUy=wb=1mt8OVFb_eGEmCLw@mail.gmail.com' \
--to=newren@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=vdye@github.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).