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

Previous thread: [PATCH] Consolidate {receive,fetch}.unpackLimit by Junio C Hamano on Wednesday, January 24, 2007 - 6:14 pm. (3 messages)

Next thread: how to test changes? by Uwe on Wednesday, January 24, 2007 - 9:27 pm. (3 messages)
From: Horst H. von Brand
Date: Wednesday, January 24, 2007 - 6:37 pm

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
-

From: Junio C Hamano
Date: Wednesday, January 24, 2007 - 6:54 pm

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 thread: [PATCH] Consolidate {receive,fetch}.unpackLimit by Junio C Hamano on Wednesday, January 24, 2007 - 6:14 pm. (3 messages)

Next thread: how to test changes? by Uwe on Wednesday, January 24, 2007 - 9:27 pm. (3 messages)