Re: [PATCH 0/7] Make alternates affect fetch behavior
On Sat, Feb 11, 2012 at 07:20:54AM +0100, mhagger@alum.mit.edu wrote:
Show 23 quoted lines
> It used to be that alternate references were not considered "complete"
> when fetching via fetch-pack. This failure was not so obvious because
> the big benefit of alternates is seen when cloning, and clone used a
> different data path: it put the alternate references into extra refs
> (which makes them look like references within the local repository).
>
> This patch series teaches fetch-pack to treat objects that are
> available via alternates as "complete".
>
> Once that is fixed, clone doesn't need to use the special extra_refs
> kludge, so change that.
>
> And once that is changed, the extra_refs API is no longer needed at
> all, so remove it.
>
> Michael Haggerty (7):
> t5700: document a failure of alternates to affect fetch
> clone.c: move more code into the "if (refs)" conditional
> fetch-pack.c: rename some parameters from "path" to "refname"
> fetch-pack.c: inline insert_alternate_refs()
> everything_local(): mark alternate refs as complete
> clone: do not add alternate references to extra_refs
> refs: remove the extra_refs API
>From my reading, all of these patches look good. Thanks for a
well-organized series.
-Peff