> Also, vfsd doesn't seem to be Google-able whereas "VFS for Git" is, and > since it's not an internal git project, it might be nice to use a name > that users can find. > > But anyway, I have no idea what the "correct" text here is (as > probably evidenced by my questions), so if anyone wants to provide > suggestions or corrections to the commit message, I'm happy to take > them. How about this? Typically with sparse checkouts, we expect files outside the sparsity patterns to be marked as SKIP_WORKTREE and be missing from the working tree. There is currently an effort code-named `vfsd` (see https://lore.kernel.org/git/20220207190320.2960362-1-jonathantanmy@xxxxxxxxxx/ for details) to implement a Git-aware virtual file system layer (similar in spirit to the VFS for Git project) that can be used to turn this expectation on its head: all files are considered present in the working copy, though they are not vivified until actually accessed. With such a virtual file system (VFS) layer, most of the files do not match the sparsity patterns at first, and the VFS layer automatically updates the sparsity patterns to add more files whenever files are written. Side note: VFS for Git itself requires the Microsoft fork of Git to work, therefore this patch would only be needed in that fork, as far as VFS for Git is concerned. Ciao, Dscho
