From: Nguyen Thai Ngoc Duy <pclouds@gmail.com>
To: Elijah Newren <newren@gmail.com>
Cc: "Shawn O. Pearce" <spearce@spearce.org>, git <git@vger.kernel.org>
Subject: Re: Sparse clones (Was: Re: [PATCH 1/2] upload-pack: support subtree packing)
Date: Thu, 29 Jul 2010 20:29:32 +1000 [thread overview]
Message-ID: <AANLkTi=-+9TbR7=McSsh55gdzfKEsdqcao67kf0yFxsr@mail.gmail.com> (raw)
In-Reply-To: <AANLkTikoOL0jYi4kD0L1uLU=UCmG9p0Rc3VLOU-djQnY@mail.gmail.com>
On Wed, Jul 28, 2010 at 1:59 PM, Elijah Newren <newren@gmail.com> wrote:
>> Revision walking is not the only gate to access objects. Others like
>> diff machinery needs also be taught about rev-list limits.
>
> Right, good point. Are there others than the diff machinery (and the
> fsck special case) that you know of?
A lot (just found out as I was pushing subtree clone as far as I
could). For merging, you can hardly limit sha1 access. When writing
tree, git's particularly paranoid and check for sha1 existence
(has_sha1_file and assert_sha1_type). You can find that has_sha1_file
is used in many places, not just commit/write-tree.
Narrow/Sparse/Subtree/Lazy/Whatever-it-is clone will have hard time..
Oh.. the lazy one does not.
--
Duy
next prev parent reply other threads:[~2010-07-29 10:29 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-28 0:13 Sparse clones (Was: Re: [PATCH 1/2] upload-pack: support subtree packing) Elijah Newren
2010-07-28 1:05 ` Avery Pennarun
2010-07-28 3:06 ` Nguyen Thai Ngoc Duy
2010-07-28 3:38 ` Nguyen Thai Ngoc Duy
2010-07-28 3:58 ` Avery Pennarun
2010-07-28 6:12 ` Sverre Rabbelier
2010-07-28 7:59 ` Nguyen Thai Ngoc Duy
2010-07-28 14:48 ` Sverre Rabbelier
2010-07-28 7:11 ` Nguyen Thai Ngoc Duy
2010-07-28 3:31 ` Elijah Newren
2010-07-31 22:36 ` Elijah Newren
2010-07-28 3:36 ` Nguyen Thai Ngoc Duy
2010-07-28 3:59 ` Elijah Newren
2010-07-29 10:29 ` Nguyen Thai Ngoc Duy [this message]
2010-08-13 17:31 ` Enrico Weigelt
2010-08-13 19:19 ` Truncating history (Re: Sparse clones) Jonathan Nieder
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='AANLkTi=-+9TbR7=McSsh55gdzfKEsdqcao67kf0yFxsr@mail.gmail.com' \
--to=pclouds@gmail.com \
--cc=git@vger.kernel.org \
--cc=newren@gmail.com \
--cc=spearce@spearce.org \
/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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).