From: Michael Lukashov <michael.lukashov@gmail.com>
To: git@vger.kernel.org
Cc: Junio C Hamano <gitster@pobox.com>
Subject: Re: [PATCH] pull --all: fix error message when current branch is not tracking remote branch
Date: Mon, 8 Mar 2010 23:26:32 +0300 [thread overview]
Message-ID: <63cde7731003081226hb27c705l9038f2dccfd1c042@mail.gmail.com> (raw)
In-Reply-To: <1267566741-5784-1-git-send-email-michael.lukashov@gmail.com>
No-one ever interested?
Thought it's useful improvement.
Instead of above-mentioned confusing message, you get
much more clearer explanation:
You asked me to pull without telling me which branch you
want to merge with, and 'branch.<>.merge' in
your configuration file does not tell me, either. Please
specify which branch you want to use on the command line and
try again (e.g. 'git pull <repository> <refspec>').
See git-pull(1) for details.
...
prev parent reply other threads:[~2010-03-08 20:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-02 21:52 [PATCH] pull --all: fix error message when current branch is not tracking remote branch Michael Lukashov
2010-03-08 20:26 ` Michael Lukashov [this message]
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=63cde7731003081226hb27c705l9038f2dccfd1c042@mail.gmail.com \
--to=michael.lukashov@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
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;
as well as URLs for NNTP newsgroup(s).