Git development
 help / color / mirror / Atom feed
From: Junio C Hamano <junkio@cox.net>
To: Erik Mouw <erik@harddisk-recovery.com>
Cc: git@vger.kernel.org
Subject: Re: Tags not transferred with git pull?
Date: Fri, 04 Nov 2005 11:26:20 -0800	[thread overview]
Message-ID: <7vll04tdsz.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: 20051104160503.GC23790@harddisk-recovery.com

Erik Mouw <erik@harddisk-recovery.com> writes:

> Ah, right. I got the impression that the latest git was supposed to do
> that automatically with a git pull.

Sorry for the confusion.  The barebone Porcelainish shipped with
git-core does not fetch and store tags unconditionally under the
same name as the remote has without being told; you need to
explicitly tell it to 'git fetch --tags'.

What was added recently was a low level support for Cogito to
implement the automatic tracking.  This is supposed to (I do not
offhand know if the Cogito side has been updated to do so
already) work a bit differently.  Instead of grabbing all tags
and all objects reachable from them, as you fetch commits from
the remote, the automatic tracking fetches tags that point at
them.  What this means is that the tags on the remote branch you
are tracking would be fetched automatically but tags on a remote
branch you are not interested in are not.

  reply	other threads:[~2005-11-04 19:26 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-04 15:53 Tags not transferred with git pull? Erik Mouw
2005-11-04 15:57 ` Jan Harkes
2005-11-04 15:59 ` Fernando J. Pereda
2005-11-04 16:05   ` Erik Mouw
2005-11-04 19:26     ` Junio C Hamano [this message]
2005-11-07 10:44       ` Erik Mouw

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=7vll04tdsz.fsf@assigned-by-dhcp.cox.net \
    --to=junkio@cox.net \
    --cc=erik@harddisk-recovery.com \
    --cc=git@vger.kernel.org \
    /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