git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: "Olsen\, Alan R" <alan.r.olsen@intel.com>
Cc: "git\@vger.kernel.org" <git@vger.kernel.org>
Subject: Re: Fetch and -t
Date: Mon, 11 Feb 2013 18:24:33 -0800	[thread overview]
Message-ID: <7v621yjmla.fsf@alter.siamese.dyndns.org> (raw)
In-Reply-To: <4B2793BF110AAB47AB0EE7B9089703854FEE40B6@fmsmsx110.amr.corp.intel.com> (Alan R. Olsen's message of "Tue, 12 Feb 2013 00:41:49 +0000")

"Olsen, Alan R" <alan.r.olsen@intel.com> writes:

> I have found that if I add a remote and do a "git fetch -t -f
> remote_name" that it *only* pulls tags.
>
> Reading the man page it seems like it should pull all the remotes
> and all the tags and the commits only reachable by tags.

This is what appears in the documentation we ship these days.

    -t::
    --tags::
            This is a short-hand for giving "refs/tags/*:refs/tags/*"
            refspec from the command line, to ask all tags to be fetched
            and stored locally.  Because this acts as an explicit
            refspec, the default refspecs (configured with the
            remote.$name.fetch variable) are overridden and not used.

http://git-htmldocs.googlecode.com/git/git-fetch.html

Previous discussion:

    http://thread.gmane.org/gmane.comp.version-control.git/180636

A more recent one:

    http://thread.gmane.org/gmane.comp.version-control.git/211439/focus=211464

  reply	other threads:[~2013-02-12  2:25 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-12  0:41 Fetch and -t Olsen, Alan R
2013-02-12  2:24 ` Junio C Hamano [this message]
2013-02-12 18:28   ` Olsen, Alan R

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=7v621yjmla.fsf@alter.siamese.dyndns.org \
    --to=gitster@pobox.com \
    --cc=alan.r.olsen@intel.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;
as well as URLs for NNTP newsgroup(s).