Re: Sparse clones (Was: Re: [PATCH 1/2] upload-pack: support subtree packing)
- From
Nguyen Thai Ngoc Duy <pclouds@gmail.com>
- Date
- Jul 29, 2010, 10:29 UTC
- Message-ID
- <AANLkTi=-+9TbR7=McSsh55gdzfKEsdqcao67kf0yFxsr@mail.gmail.com>
- In-Reply-To
- <AANLkTikoOL0jYi4kD0L1uLU=UCmG9p0Rc3VLOU-djQnY@mail.gmail.com>
On Wed, Jul 28, 2010 at 1:59 PM, Elijah Newren <newren@gmail.com> wrote:
Show 5 quoted lines
>> 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