Re: [PATCH 08/15] scalar: implement the `clone` subcommand

From: Elijah Newren <newren@gmail.com>
Date: Sep 28, 2021, 05:19 UTC
Message-ID: <CABPp-BH0U9+KEHTuMdfu-jhL+y3eRzjyfuRzWy9-jGxka8PH+Q@mail.gmail.com>
In-Reply-To: <2cbf0b611133df5fa7eed1bf38460f9d119d2a6e.1630359290.git.gitgitgadget@gmail.com>

On Mon, Aug 30, 2021 at 2:36 PM Johannes Schindelin via GitGitGadget <gitgitgadget@gmail.com> wrote:

...

Show 17 quoted lines

>  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?