git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Derrick Stolee <stolee@gmail.com>
To: Junio C Hamano <gitster@pobox.com>, git@vger.kernel.org
Subject: Re: What's cooking in git.git (May 2021, #02; Wed, 12)
Date: Wed, 12 May 2021 09:03:28 -0400	[thread overview]
Message-ID: <05932ebc-04ac-b3c5-a460-5d37d8604fd9@gmail.com> (raw)
In-Reply-To: <xmqqo8dgfl8l.fsf@gitster.g>

On 5/12/2021 3:46 AM, Junio C Hamano wrote:

> * ds/status-with-sparse-index (2021-04-28) 10 commits
>  - fsmonitor: test with sparse index
>  - status: use sparse-index throughout
>  - status: skip sparse-checkout percentage with sparse-index
>  - dir.c: accept a directory as part of cone-mode patterns
>  - unpack-trees: stop recursing into sparse directories
>  - unpack-trees: compare sparse directories correctly
>  - unpack-trees: preserve cache_bottom
>  - t1092: add tests for status/add and sparse files
>  - Merge branch 'mt/add-rm-in-sparse-checkout' into ds/status-with-sparse-index
>  - Merge branch 'ds/sparse-index-protections' into ds/status-with-sparse-index
> 
>  "git status" codepath learned to work with sparsely populated index
>  without hydrating it fully.
> 
>  What's the status of this thing?

There has been no review on the simplified v2. But also I've been working
to integrate the sparse-index work into our Scalar functional tests and
have found some issues with the series. I'm working through those issues
now and will send a v3 when I'm ready. Feel free to eject it until then.

Thanks,
-Stolee

  reply	other threads:[~2021-05-12 13:03 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-12  7:46 Junio C Hamano
2021-05-12 13:03 ` Derrick Stolee [this message]
2021-05-12 16:35 ` Elijah Newren

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=05932ebc-04ac-b3c5-a460-5d37d8604fd9@gmail.com \
    --to=stolee@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --subject='Re: What'\''s cooking in git.git (May 2021, #02; Wed, 12)' \
    /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

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 NNTP newsgroup(s).