Kevin Willford <kewi...@microsoft.com> writes: > When using the sparse checkout feature the git reset command 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 have been changed but there is nothing that is in the > working directory. This will cause the next status call to show either > deleted for files modified or deleting or nothing for files added.
Getting rid of sparseness may of course be one way to correct the discrepancy, but it is unclear to me if that is the best way to do so. An alternative may be to add entries to the index that does have the bit on for paths that are meant to be skipped due to "sparse" thing, no? Am I being naive, missing some reason why that would give us a worse result?
