# Fetch and -t 3 messages from 2013-02-12 to 2013-02-12. Participants: Olsen, Alan R, Junio C Hamano. Thread: https://gitlist.dev/t/32882 ## Olsen, Alan R, 2013-02-12 00:41 Subject: Fetch and -t Message-ID: <4B2793BF110AAB47AB0EE7B9089703854FEE40B6@fmsmsx110.amr.corp.intel.com> URL: https://gitlist.dev/e/4B2793BF110AAB47AB0EE7B9089703854FEE40B6%40fmsmsx110.amr.corp.intel.com ``` 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. Am I misreading this or it supposed to work this way. I don't mind doing two fetches to get everything, but the documentation needs to be a little clearer. ``` ## Junio C Hamano, 2013-02-12 02:24 Subject: Re: Fetch and -t Message-ID: <7v621yjmla.fsf@alter.siamese.dyndns.org> URL: https://gitlist.dev/e/7v621yjmla.fsf%40alter.siamese.dyndns.org In-Reply-To: <4B2793BF110AAB47AB0EE7B9089703854FEE40B6@fmsmsx110.amr.corp.intel.com> ``` "Olsen, Alan R" 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 ``` ## Olsen, Alan R, 2013-02-12 18:28 Subject: RE: Fetch and -t Message-ID: <4B2793BF110AAB47AB0EE7B9089703854FEE45E9@fmsmsx110.amr.corp.intel.com> URL: https://gitlist.dev/e/4B2793BF110AAB47AB0EE7B9089703854FEE45E9%40fmsmsx110.amr.corp.intel.com In-Reply-To: <7v621yjmla.fsf@alter.siamese.dyndns.org> ``` [Sorry for the top-posting. I *hate* Outlook.] I will need to check why my system is showing old man pages. I am running something compiled from the git tree on kernel.org. Thanks! -----Original Message----- From: Junio C Hamano [mailto:gitster@pobox.com] Sent: Monday, February 11, 2013 6:25 PM To: Olsen, Alan R Cc: git@vger.kernel.org Subject: Re: Fetch and -t "Olsen, Alan R" 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 ```