Re: What's cooking in git.git (Jun 2021, #05; Tue, 15)

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Tue, Jun 15, 2021 at 1:24 AM Junio C Hamano <gitster@xxxxxxxxx> wrote:
>
> * ds/status-with-sparse-index (2021-05-22) 14 commits
>  - fsmonitor: integrate with sparse index
>  - wt-status: expand added sparse directory entries
>  - 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: be careful around sparse directory entries
>  - unpack-trees: compare sparse directories correctly
>  - unpack-trees: preserve cache_bottom
>  - t1092: add tests for status/add and sparse files
>  - t1092: expand repository data shape
>  - sparse-index: include EXTENDED flag when expanding
>  - sparse-index: skip indexes with unmerged entries
>  - 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.
>
>  Waiting for reviews.

I reviewed each of the rounds except v4 (v5 is the latest), and
generally like the series but I highlighted a few issues in v5.
Stolee reported he's planning to send a re-roll (see e.g.
https://lore.kernel.org/git/2784d29b-b22a-2bf6-2450-7b4a0a72df54@xxxxxxxxx/),
so I think this can be updated to "expecting a reroll"?



[Index of Archives]     [Linux Kernel Development]     [Gcc Help]     [IETF Annouce]     [DCCP]     [Netdev]     [Networking]     [Security]     [V4L]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux SCSI]     [Fedora Users]

  Powered by Linux