Re: sparse fetch, was Re: [PATCH 08/12] git-clone: support --path to do sparse clone

From: Sverre Rabbelier <alturin@gmail.com>
Date: Jul 24, 2008, 19:01 UTC
Message-ID: <bd6139dc0807241201v50cd5ef2m58ee7efc05119e20@mail.gmail.com>
In-Reply-To: <20080724185332.GQ32184@machine.or.cz>

On Thu, Jul 24, 2008 at 8:53 PM, Petr Baudis <pasky@suse.cz> wrote:

>  I don't follow how these two issues arise, if the server will do the
> pruning for you. It will just skip entering some tree objects when doing
> object traversal; why opening the git protocol or faking commits? This
> would be a simple extra capability in the protocol.

Wouldn't that be as simple as passing a pathspec to git-rev-list? Not a lot of overhead there I reckon.

> One question is what to do with delta chains including unwanted
> objects, but I think that given the objects' associativity for delta
> chains, this shouldn't be huge practical issues and it could be
> affordable in principle to include even unwanted objects.

Just keep them? What we're doing here is trying to optimize in the case that someone has a sparse checkout, nothing bad will happen if they get too many info surely? (Save for them not getting as much improvement as would have been possible would the pack have been created differently.)

-- 
Cheers,

Sverre Rabbelier