On 8/23/2019 7:02 PM, Elijah Newren wrote: > On Tue, Aug 20, 2019 at 8:13 AM Derrick Stolee via GitGitGadget > <gitgitgad...@gmail.com> wrote: >> >> From: Derrick Stolee <dsto...@microsoft.com> >> >> Getting started with a sparse-checkout file can be daunting. Help >> users start their sparse enlistment using 'git sparse-checkout init'. >> This will set 'core.sparseCheckout=true' in their config, write >> an initial set of patterns to the sparse-checkout file, and update >> their working directory. >> >> Using 'git read-tree' to clear directories does not work cleanly >> on Windows, so manually delete directories that are tracked by Git >> before running read-tree. > > Is that a bug in read-tree that needs to be fixed?
Just to follow up on this: it turns out that this is NOT a bug in read-tree, but rather a side-effect of our custom "core.gvfs" config setting. In the virtualized world, we didn't want Git to hard-delete a folder just because we marked everything sparse. By removing that option from my environment, the deletions work as expected. Thanks, -Stolee
