git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Nguyen Thai Ngoc Duy" <pclouds@gmail.com>
To: "Jeff King" <peff@peff.net>
Cc: git@vger.kernel.org
Subject: Re: [PATCH 08/12] git-clone: support --path to do sparse clone
Date: Fri, 25 Jul 2008 01:47:54 +0700	[thread overview]
Message-ID: <fcaeb9bf0807241147k1175c8a3mffc12e3b3cc1aa3f@mail.gmail.com> (raw)
In-Reply-To: <20080724171952.GB21043@sigill.intra.peff.net>

On 7/25/08, Jeff King <peff@peff.net> wrote:
> On Wed, Jul 23, 2008 at 09:57:18PM +0700, Nguyen Thai Ngoc Duy wrote:
>
>  > +             if (option_sparse_prefix) {
>  > +                     git_config_set("core.sparsecheckout", option_sparse_prefix);
>  > +                     set_sparse_prefix(option_sparse_prefix);
>  > +             }
>  > +
>
>
> As a user, I would expect "sparse clone" to also be sparse on the
>  fetching. That is, to not even bother fetching tree objects that we are
>  not going to check out. But that is a whole other can of worms from
>  local sparseness, so I think it is worth saving for a different series.
>
>  So instead I would suggest that this be mentioned in the documentation
>  for --path, but there doesn't seem to be any.

Thanks. Will mention it when I write documentation for this.
-- 
Duy

      parent reply	other threads:[~2008-07-24 18:48 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-23 14:57 [PATCH 10/12] git-checkout: support --full and --path to manipulate sparse checkout Nguyễn Thái Ngọc Duy
2008-07-23 14:57 ` [PATCH 08/12] git-clone: support --path to do sparse clone Nguyễn Thái Ngọc Duy
2008-07-23 14:56   ` [PATCH 03/12] Introduce sparse prefix Nguyễn Thái Ngọc Duy
2008-07-23 14:55     ` [PATCH 02/12] git-grep: support --no-external-grep Nguyễn Thái Ngọc Duy
2008-07-23 19:01       ` Petr Baudis
2008-07-23 19:05         ` Petr Baudis
2008-07-24 20:26       ` Alex Riesen
2008-07-24 23:16         ` Nguyen Thai Ngoc Duy
2008-07-24 17:19   ` [PATCH 08/12] git-clone: support --path to do sparse clone Jeff King
2008-07-24 17:41     ` sparse fetch, was " Johannes Schindelin
2008-07-24 18:28       ` Jeff King
2008-07-25  0:09         ` Johannes Schindelin
2008-07-25  0:46         ` James Pickens
2008-07-25  0:49           ` sparse fetch, was Re: [PATCH 08/12] git-clone: support --path?to " Jeff King
2008-07-25  8:47         ` sparse fetch, was Re: [PATCH 08/12] git-clone: support --path to " Junio C Hamano
2008-07-25  8:54           ` Sverre Rabbelier
2008-07-24 18:44       ` Nguyen Thai Ngoc Duy
2008-07-24 18:53       ` Petr Baudis
2008-07-24 19:01         ` Sverre Rabbelier
2008-07-25  0:12           ` Johannes Schindelin
2008-07-25  0:42             ` Petr Baudis
2008-07-25  8:14             ` Sverre Rabbelier
2008-07-24 18:47     ` Nguyen Thai Ngoc Duy [this message]

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=fcaeb9bf0807241147k1175c8a3mffc12e3b3cc1aa3f@mail.gmail.com \
    --to=pclouds@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=peff@peff.net \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).