Re: RFC: Design and code of partial clones (now, missing commits and trees OK) (part 2/3)

From: Jonathan Tan <jonathantanmy@google.com>
Date: Sep 22, 2017, 22:52 UTC
Message-ID: <20170922155235.7b50de91f0370d9101cc4faa@google.com>
In-Reply-To: <5b251b02-fe00-3d99-8ae2-d6df0193ebe0@jeffhostetler.com>

On Fri, 22 Sep 2017 17:19:50 -0400 Jeff Hostetler <git@jeffhostetler.com> wrote:

Show 8 quoted lines

> > In your specific example, how would rev-list know, on the client, to
> > include (or exclude) a large blob in its output if it does not have it,
> > and thus does not know its size?
> > 
> 
> The client doesn't have the size. It just knows it is missing and it
> needs it. It doesn't matter why it is missing.  (But I guess the client
> could assume it is because it is large.)

Ah, OK.

> So rev-list on the client could filter the objects it has by size.

My issue is that if the purpose of this feature in rev-list is to do prefetching, the only criterion we need to check for is absence from the local repo right? (Or is filtering by size on the client useful for other reasons?)

> FYI I just posted my RFC this afternoon.
> https://public-inbox.org/git/20170922204211.GA24036@google.com/T/

Thanks, I'll take a look.