git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: Creating sparse checkout in a new linked git worktree

From
Eric Sunshine <sunshine@sunshineco.com>
Date
Jan 30, 2018, 19:00 UTC
Message-ID
<CAPig+cRiyterpyJfayVmA5Ra_zzyVp6GGSNqe2Tx-Hrrif+U8A@mail.gmail.com>
In-Reply-To
<615c04025165d0dff9d6e6b66bf11a41.squirrel@mail.jessiehernandez.com>

On Tue, Jan 30, 2018 at 9:25 AM, Jessie Hernandez <git@jessiehernandez.com> wrote:

Show 6 quoted lines
>> The sparse-checkout file is specific to each worktree, which allows you
> to control "sparsity" on a worktree by worktree basis. Therefore, you
> should create $GIT_DIR/worktrees/<id>/info/sparse-checkout instead
> (where <id> is "new-branch" in your example).
>
> Would it help if this was added to the documentation of git-read-tree

It probably would. Would you be interested in submitting a patch (mentioning 'git rev-parse --git-path info/sparse-checkout', as suggested by Duy)?

Previous: Jessie HernandezNext: Jessie Hernandez
Message 2 of 3 in “Re: Creating sparse checkout in a new linked git worktree”
  1. Jessie HernandezJan 30, 2018
  2. Eric SunshineJan 30, 2018
  3. Jessie HernandezJan 31, 2018

Read the whole thread, see it on lore, or plain text.

$ 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.