# git-1.5.0.rc2: "git pull -t" complains 2 messages from 2007-01-25 to 2007-01-25. Participants: Horst H. von Brand, Junio C Hamano. Thread: https://gitlist.dev/t/6514 ## Horst H. von Brand, 2007-01-25 01:37 Subject: git-1.5.0.rc2: "git pull -t" complains Message-ID: <200701250137.l0P1bRYm020504@laptop13.inf.utfsm.cl> URL: https://gitlist.dev/e/200701250137.l0P1bRYm020504%40laptop13.inf.utfsm.cl ``` I've got a repo here which is missing oldish tags, so I: $ git pull -t Warning: No merge candidate found because value of config option "branch.master.merge" does not match any remote branch fetched. No changes. Both "git pull --help" and git-pull(1) say this should work. -- Dr. Horst H. von Brand User #22616 counter.li.org Departamento de Informatica Fono: +56 32 2654431 Universidad Tecnica Federico Santa Maria +56 32 2654239 Casilla 110-V, Valparaiso, Chile Fax: +56 32 2797513 ``` ## Junio C Hamano, 2007-01-25 01:54 Subject: Re: git-1.5.0.rc2: "git pull -t" complains Message-ID: <7vwt3ban27.fsf@assigned-by-dhcp.cox.net> URL: https://gitlist.dev/e/7vwt3ban27.fsf%40assigned-by-dhcp.cox.net In-Reply-To: <200701250137.l0P1bRYm020504@laptop13.inf.utfsm.cl> ``` "Horst H. von Brand" writes: > I've got a repo here which is missing oldish tags, so I: > > $ git pull -t > Warning: No merge candidate found because value of config option > "branch.master.merge" does not match any remote branch fetched. > No changes. > > Both "git pull --help" and git-pull(1) say this should work. Ah, that's because git-pull documentation shares large part of the source with git-fetch (the part that talk about --tags is coming from a single file, pull-fetch-param.txt). It really shouldn't. Fetching all tags and merging them all to your current branch does not make any sense. ```