Re: Two-step tag fetching

From: Shawn O. Pearce <spearce@spearce.org>
Date: Aug 11, 2008, 02:43 UTC
Message-ID: <20080811024341.GA27195@spearce.org>
In-Reply-To: <alpine.LNX.1.10.0808101124370.1727@fbirervta.pbzchgretzou.qr>

Jan Engelhardt <jengelh@medozas.de> wrote:

Show 7 quoted lines

> On Sunday 2008-08-10 11:19, Jan Engelhardt wrote:
> >
> >I have a somewhat older development tree at git://dev.medozas.de/linux 
> >(about 2.6.26-rc6), and without any tags. Now, adding in Linus's 
> >repository makes it gather all the new stuff, and all the missing tags:
> >[...]
> >What interests me here is why there are two "From" lines.

...

Show 5 quoted lines

> And my suspicion is that v2.6.19.1--v2.6.19.6 have been repacked into 
> packed-refs, and v2.6.19.7 has been added later and is a loose tag (as 
> is the master branch). So the packed-refs (with less recent history) are 
> fetched later, which conflicts with the output from Linus's repo where I 
> get the (possibly packed) tags first, in chronological order.

Sort of, but not really.

The remote server running git:// must not be new enough to support the include-tag extension. So fetching tags which the client does not have the objects for, and which the client isn't 100% sure it will need to fetch have to be done during the second pass, which is when the second From line is displayed.

These tags caught during the second pass are tags pointing at much older commits; commits which no active branch is currently pointing at directly, but which are reachable indirectly. That is why you are seeing this second pass pick up the "older" tags.

-- 
Shawn.