Re: warning merge message
- From
- Josef Weidendorfer <josef.weidendorfer@gmx.de>
- Date
- Dec 22, 2006, 20:42 UTC
- Message-ID
- <200612222142.15489.Josef.Weidendorfer@gmx.de>
- In-Reply-To
- <7v1wms79mg.fsf@assigned-by-dhcp.cox.net>
On Friday 22 December 2006 07:00, Junio C Hamano wrote:
Show 13 quoted lines
> Junio C Hamano <junkio@cox.net> writes: > > > Luben Tuikov <ltuikov@yahoo.com> writes: > > > >> Can we please eliminate this message: > >> Warning: No merge candidate found because value of config option > >> "branch.master.merge" does not match any remote branch fetched. > > > > The above message was meant only for "git pull", but was leaked > > even when you did "git fetch"; it was a bug and was corrected > > already (hopefully). > > Gaah... it turns out that it was not fixed properly.
Sorry, I am missing something. What is the exact problem that goes wrong here?
The message is printed when "git pull [args]" does not result in any merge with current branch. What is wrong about this? But a "git pull ..." always should lead to some merge in the end in every possible work flow, or should it not?
Josef