Re: [PATCH 1/1] sparse-checkout: list folders in cone mode
- From
Junio C Hamano <gitster@pobox.com>
- Date
- Dec 26, 2019, 21:17 UTC
- Message-ID
- <xmqqo8vukcqv.fsf@gitster-ct.c.googlers.com>
- In-Reply-To
- <07be7b8dda679d79ac9b218b2a9b08e47d7762fd.1577393347.git.gitgitgadget@gmail.com>
"Derrick Stolee via GitGitGadget" <gitgitgadget@gmail.com> writes:
> From: Derrick Stolee <dstolee@microsoft.com>
> Subject: Re: [PATCH 1/1] sparse-checkout: list folders in cone mode
s/folder/directory/ everywhere as the rest of Git.
> When core.sparseCheckoutCone is enabled, the 'git sparse-checkout set' > command taks a list of folders as input, then creates an ordered
"takes"
> list of sparse-checkout patterns such that those folders are > recursively included and all sibling blobs along the parent folders
In this sentence, what does a "blob" really mean? Do you mean a filesystem entity, that is not a folder, that is immediately contained in the "parent folder" (in other words, regular files and symbolic links)?
How would this interact with a submodule by the way?
Show 16 quoted lines
> are also included. Listing the patterns is less user-friendly than the > folders themselves. > > In cone mode, and as long as the patterns match the expected cone-mode > pattern types, change the output of 'git sparse-checkout list' to only > show the folders that created the patterns. > ... > +In the cone mode case, the `git sparse-checkout list` subcommand will list the > +folders that define the recursive patterns. For the example sparse-checkout file > +above, the output is as follows: > + > +-------------------------- > +$ git sparse-checkout list > +A/B/C > +-------------------------- > +
Sounds like a worthwhile usability improvement.