{"thread":{"id":"23390","subject":"Re: question about sparse checkout","startedAt":"2010-04-09T11:13:13Z","lastAt":"2010-04-09T11:13:13Z","messageCount":1,"participants":["Nguyen Thai Ngoc Duy"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"139027","messageId":"j2hfcaeb9bf1004090413ud934f42ch633b04e4b282b3f@mail.gmail.com","threadId":"23390","inReplyTo":"i2t8ba6bed41004090318k265095e9i72c9c1e79b3bfcd7@mail.gmail.com","subject":"Re: question about sparse checkout","fromName":"Nguyen Thai Ngoc Duy","fromEmail":"pclouds@gmail.com","sentAt":"2010-04-09T11:13:13Z","receivedAt":"2010-04-09T11:13:13Z","isPatch":false,"sender":{"key":"pclouds@gmail.com","avatar":"https://avatars.githubusercontent.com/u/720?v=4"},"body":"On Fri, Apr 9, 2010 at 12:18 PM, Matt Rice <ratmice@gmail.com> wrote:\n> hi,\n>\n> is there some way that cloning a sparse checkout can also clone the\n> sparsity of the checkout?\n\nNo. The sparsity is a property of worktree, it can't be cloned.\n\n> currently, when cloning, I have to set up the sparsity on each cloned\n> repository, after fetching\n> by providing something like a shell script for each 'view' of the repository\n> just wondering if there was a way to make this a transferrable property.\n\nI have a similar problem (transferring remote.* by cloning). Maybe we\ncould extend git protocol a little bit to allow these customizations?\n-- \nDuy\n"}]}