Re: [PATCH] reset: behave correctly with sparse-checkout

[Derrick Stolee <stolee@gmail.com>]

On 9/28/2021 11:20 AM, Derrick Stolee via GitGitGadget wrote:
> From: Kevin Willford <kewillf@microsoft.com>
> 
> When using the sparse checkout feature, 'git reset' will add entries to
> the index that will have the skip-worktree bit off but will leave the
> working directory empty. File data is lost because the index version of
> the files has been changed but there is nothing that is in the working
> directory. This will cause the next 'git status' call to show either
> deleted for files modified or deleting or nothing for files added. The
> added files should be shown as untracked and modified files should be
> shown as modified.

Sorry for the noise, but hold off on this patch. It will be joining
a larger series involving getting 'git reset' working with the sparse
index.

Thanks,
-Stolee