threads / discuss / 6514

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

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

## tl;dr

2 messages between Jan 25, 2007 and Jan 25, 2007.

replies: 1people: 2as markdown or json

Horst H. von Brand· Jan 25, 2007, 01:37 UTC · lore

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· Jan 25, 2007, 01:54 UTC · re: Horst H. von Brand · lore

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

"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.