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

Re: question about sparse checkout

From
Nguyen Thai Ngoc Duy <pclouds@gmail.com>
Date
Apr 9, 2010, 11:13 UTC
Message-ID
<j2hfcaeb9bf1004090413ud934f42ch633b04e4b282b3f@mail.gmail.com>
In-Reply-To
<i2t8ba6bed41004090318k265095e9i72c9c1e79b3bfcd7@mail.gmail.com>
On Fri, Apr 9, 2010 at 12:18 PM, Matt Rice <ratmice@gmail.com> wrote:
> hi,
>
> is there some way that cloning a sparse checkout can also clone the
> sparsity of the checkout?
No. The sparsity is a property of worktree, it can't be cloned.
> currently, when cloning, I have to set up the sparsity on each cloned
> repository, after fetching
> by providing something like a shell script for each 'view' of the repository
> just wondering if there was a way to make this a transferrable property.

I have a similar problem (transferring remote.* by cloning). Maybe we could extend git protocol a little bit to allow these customizations?

-- 
Duy
Message 1 of 1 in “Re: question about sparse checkout”
  1. Nguyen Thai Ngoc DuyApr 9, 2010

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.