All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nguyen Thai Ngoc Duy <pclouds@gmail.com>
To: Matt Rice <ratmice@gmail.com>, Git Mailing List <git@vger.kernel.org>
Subject: Re: question about sparse checkout
Date: Fri, 9 Apr 2010 13:13:13 +0200	[thread overview]
Message-ID: <j2hfcaeb9bf1004090413ud934f42ch633b04e4b282b3f@mail.gmail.com> (raw)
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

           reply	other threads:[~2010-04-09 11:13 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <i2t8ba6bed41004090318k265095e9i72c9c1e79b3bfcd7@mail.gmail.com>]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=j2hfcaeb9bf1004090413ud934f42ch633b04e4b282b3f@mail.gmail.com \
    --to=pclouds@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=ratmice@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.