threads / discuss / 47720

Re: Creating sparse checkout in a new linked git worktree

Subject: Re: Creating sparse checkout in a new linked git worktree

## tl;dr

3 messages between Jan 30, 2018 and Jan 31, 2018.

replies: 2people: 2as markdown or json

Jessie Hernandez· Jan 30, 2018, 14:25 UTC · lore
> On Wed, Jan 24, 2018 at 11:11 AM, Jessie Hernandez
> <git@jessiehernandez.com> wrote:
>> I am trying to get a sparse checkout in a linked worktree but cannot
get
Show 10 quoted lines
>> it working. I have tried the following
>> * git worktree add /some/new/path/new-branch --no-checkout
>> * git config core.sparseCheckout true
>> * <add the directory I would like to checkout out to
>> $GIT_DIR/info/sparse-checkout>
>> * cd  /some/new/path/new-branch
>> * git read-tree -mu sparse-checkout
>> But I still end up with a fully populated worktree.
>> Is there something I am missing or doing wrong?
> 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).

Right this seems to work indeed. Thank you.

Would it help if this was added to the documentation of git-read-tree

Regards, Jessie

Eric Sunshine· Jan 30, 2018, 19:00 UTC · re: Jessie Hernandez · lore

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

Jessie Hernandez· Jan 31, 2018, 10:03 UTC · re: Eric Sunshine · lore
Show 13 quoted lines
> On Tue, Jan 30, 2018 at 9:25 AM, Jessie Hernandez
> <git@jessiehernandez.com> wrote:
>>> 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)?
>
Sure. I will give it a try.

← back to recent threads