Re: [PATCH v3 7/8] fetch: fetch objects by their exact SHA-1 object names

From: Junio C Hamano <gitster@pobox.com>
Date: Feb 5, 2013, 15:55 UTC
Message-ID: <7vk3qmvjpd.fsf@alter.siamese.dyndns.org>
In-Reply-To: <20130205091938.GB24973@sigill.intra.peff.net>

Jeff King <peff@peff.net> writes:

Show 8 quoted lines

> On Wed, Jan 30, 2013 at 10:45:41AM -0800, Junio C Hamano wrote:
>
>> Teach "git fetch" to accept an exact SHA-1 object name the user may
>> obtain out of band on the LHS of a pathspec, and send it on a "want"
>> message when the server side advertises the allow-tip-sha1-in-want
>> capability.
>
> Hmm. The UI on this is a little less nice than I would have hoped.

Naming with unadvertised *refname*, not object name, needs protocol extension for the serving side to expand the name to object name; otherwise the receiving end wouldn't know what tip what it asked resulted in.

And that belongs to a separate "expand refs" extension (aka "delaying ref advertisement") that is outside the scope of this series but can be built on top, as I said in the cover letter.