From: "Shawn O. Pearce" <spearce@spearce.org>
To: Jan Engelhardt <jengelh@medozas.de>
Cc: git@vger.kernel.org
Subject: Re: Two-step tag fetching
Date: Sun, 10 Aug 2008 19:43:41 -0700 [thread overview]
Message-ID: <20080811024341.GA27195@spearce.org> (raw)
In-Reply-To: <alpine.LNX.1.10.0808101124370.1727@fbirervta.pbzchgretzou.qr>
Jan Engelhardt <jengelh@medozas.de> wrote:
> 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.
...
> 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.
prev parent reply other threads:[~2008-08-11 2:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-10 15:19 Two-step tag fetching Jan Engelhardt
2008-08-10 15:27 ` Jan Engelhardt
2008-08-11 2:43 ` Shawn O. Pearce [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20080811024341.GA27195@spearce.org \
--to=spearce@spearce.org \
--cc=git@vger.kernel.org \
--cc=jengelh@medozas.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).