git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: git-1.5.0.rc2: "git pull -t" complains

From
Junio C Hamano <junkio@cox.net>
Date
Jan 25, 2007, 01:54 UTC
Message-ID
<7vwt3ban27.fsf@assigned-by-dhcp.cox.net>
In-Reply-To
<200701250137.l0P1bRYm020504@laptop13.inf.utfsm.cl>
"Horst H. von Brand" <vonbrand@inf.utfsm.cl> writes:
Show 8 quoted lines
> 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.

Previous: Horst H. von Brand
Message 2 of 2 in “git-1.5.0.rc2: "git pull -t" complains”
  1. Horst H. von BrandJan 25, 2007
  2. Junio C HamanoJan 25, 2007

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.