Re: [PATCH v3 03/17] clone: add --sparse mode

From: Elijah Newren <newren@gmail.com>
Date: Oct 11, 2019, 22:20 UTC
Message-ID: <CABPp-BEcS2fT8XyrU+cghbN5YwO97HR5+xgi5=dGZPJ8ut+eUQ@mail.gmail.com>
In-Reply-To: <c8587a1fb0e335f9cbafdbb44b20d02a1e57886b.1570478905.git.gitgitgadget@gmail.com>

On Mon, Oct 7, 2019 at 1:08 PM Derrick Stolee via GitGitGadget <gitgitgadget@gmail.com> wrote:

> During the 'git sparse-checkout init' call, we must first look
> to see if HEAD is valid, since 'git clone' does not have a valid
> HEAD.

...does not have a valid HEAD by the time git_sparse_checkout_init() is called?

> The first checkout will create the HEAD ref and update the
> working directory correctly.

Is this checkout you reference a manual-initiated user checkout after the clone, or the checkout performed as part of the clone? (I'm almost certain it's the latter, but your wording makes me question.)

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.