On Tue, Dec 02, 2014 at 09:45:06AM -0800, Junio C Hamano wrote:
> Jeff King <peff@xxxxxxxx> writes:
>
> > For a public repository, it might make sense to provide a config option
> > to loosen the is_our_ref check completely (i.e., to just has_sha1_file).
> > But such an option does not yet exist.
>
> In principle, yes, but that cannot be has_sha1_file(); it has to
> have a fully connected healthy history behind it.
I thought about that, but I wonder if it matters whether we check up
front. We are not advertising it, but only trying our best to fulfill
the "want" from the other side. So either:
1. We check immediately whether we have the full history behind it,
and reject the "want" otherwise.
2. We start pack-objects on it, and the first thing it will do is
collect the full set of objects to send. If it doesn't have them,
it will barf.
Probably (1) would produce nicer error messages, but (2) is a lot more
efficient.
I dunno. I am not volunteering to implement, so I will leave thinking on
it more to somebody who wants to do so. :)
-Peff
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html