From: Junio C Hamano <junkio@cox•net>
To: Luben Tuikov <ltuikov@yahoo•com>
Cc: git@vger•kernel.org
Subject: Re: warning merge message
Date: Thu, 21 Dec 2006 16:49:09 -0800 [thread overview]
Message-ID: <7vr6us92m2.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <867728.44872.qm@web31814.mail.mud.yahoo.com> (Luben Tuikov's message of "Wed, 20 Dec 2006 13:22:59 -0800 (PST)")
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).
next prev parent reply other threads:[~2006-12-22 0:49 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-20 21:22 warning merge message Luben Tuikov
2006-12-21 9:23 ` Johannes Schindelin
2006-12-22 0:25 ` Luben Tuikov
2006-12-22 0:43 ` Shawn Pearce
2006-12-22 0:49 ` Junio C Hamano [this message]
2006-12-22 6:00 ` Junio C Hamano
2006-12-22 20:42 ` Josef Weidendorfer
2006-12-22 21:12 ` Junio C Hamano
2006-12-22 22:49 ` Josef Weidendorfer
2006-12-22 23:00 ` Junio C Hamano
2006-12-23 0:05 ` Josef Weidendorfer
-- strict thread matches above, loose matches on Subject: below --
2006-12-20 21:34 Luben Tuikov
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=7vr6us92m2.fsf@assigned-by-dhcp.cox.net \
--to=junkio@cox$(echo .)net \
--cc=git@vger$(echo .)kernel.org \
--cc=ltuikov@yahoo$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox