Re: What's cooking in git.git (Jan 2022, #04; Fri, 14)

From: Junio C Hamano <gitster@pobox.com>
Date: Jan 17, 2022, 18:30 UTC
Message-ID: <xmqq35lmw6xw.fsf@gitster.g>
In-Reply-To: <CABPp-BEROAzba2jDrBhyq1tzZZDYUqROAUGTNp4fNOHfYB3vOg@mail.gmail.com>

Elijah Newren <newren@gmail.com> writes:

Show 22 quoted lines

> On Sat, Jan 15, 2022 at 9:25 AM Junio C Hamano <gitster@pobox.com> wrote:
>>
>> * en/present-despite-skipped (2022-01-14) 6 commits
>>  - Accelerate clear_skip_worktree_from_present_files() by caching
>>  - Update documentation related to sparsity and the skip-worktree bit
>>  - repo_read_index: clear SKIP_WORKTREE bit from files present in worktree
>>  - unpack-trees: fix accidental loss of user changes
>>  - t1011: add testcase demonstrating accidental loss of user modifications
>>  - Merge branch 'vd/sparse-clean-etc' into en/present-despite-skipped
>>  (this branch uses vd/sparse-clean-etc.)
>>
>>  (NEEDSWORK: BY DOING WHAT), cope better with files on the working
>>  tree that should not exist according to the sparse checkout
>>  settings.
>>  source: <pull.1114.v2.git.1642175983.gitgitgadget@gmail.com>
>
> Perhaps:
>
> In sparse-checkouts, files mis-marked as missing from the working tree
> could lead to later problems.  Such files were hard to discover, and
> harder to correct.  Automatically detecting and correcting the marking
> of such files has been added to avoid these problems.

Thanks.