Hi Elijah, On Mon, 27 Sep 2021, Elijah Newren wrote: > On Mon, Aug 30, 2021 at 2:36 PM Johannes Schindelin via GitGitGadget > <gitgitgadget@xxxxxxxxx> wrote: > > > ... > > COMMANDS > > -------- > > > > +Clone > > +~~~~~ > > + > > +clone [<options>] <url> [<enlistment>]:: > > + Clones the specified repository, similar to linkgit:git-clone[1]. By > > + default, only commit and tree objects are cloned. Once finished, the > > + worktree is located at `<enlistment>/src`. > > ++ > > +The sparse-checkout feature is enabled (except when run with `--full-clone`) > > +and the only files present are those in the top-level directory. Use > > +`git sparse-checkout set` to expand the set of directories you want to see, > > +or `git sparse-checkout disable` to expand to all files (see > > +linkgit:git-sparse-checkout[1] for more details). You can explore the > > +subdirectories outside your sparse-checkout by using `git ls-tree HEAD`. > > Should this be `git ls-tree [-r] HEAD`? Do you expect people to just > add directories that are found immediately under the toplevel, rather > than some that are a bit deeper? I fear that `git ls-tree -r HEAD` in any monorepo might be a bit too overwhelming for any reader. But I agree that just looking at HEAD is probably not enough. Maybe we should use `git ls-tree HEAD[:<dir>]`? Ciao, Dscho
