From: "Björn Steinbrink" <B.Steinbrink@gmx.de>
To: Reece Dunn <msclrhd@googlemail.com>
Cc: Git List <git@vger.kernel.org>
Subject: Re: Running 'git pull' from an unnamed branch
Date: Mon, 6 Apr 2009 00:08:55 +0200 [thread overview]
Message-ID: <20090405220855.GA20356@atjola.homenet> (raw)
In-Reply-To: <3f4fd2640904051433u199587c3wc9bf080d138944e7@mail.gmail.com>
On 2009.04.05 22:33:57 +0100, Reece Dunn wrote:
> $ git pull
> 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
> name which branch you want to merge on the command line and
> try again (e.g. 'git pull <repository> <refspec>').
> See git-pull(1) for details on the refspec.
>
> If you often merge with the same branch, you may want to
> configure the following variables in your configuration
> file:
>
> branch..remote = <nickname>
> branch..merge = <remote-ref>
> remote.<nickname>.url = <url>
> remote.<nickname>.fetch = <refspec>
>
> See git-config(1) for details.
>
> $ git branch
> * (no branch)
> master
>
> Running `git checkout master && git pull` fixed the above issue. The
> patch below improves the error message for users that are in this
> state.
It doesn't "fix" anything, you're simply doing something different.
"git pull" while on a detached HEAD can't work, there are no defaults
that could be used. But e.g. "git pull origin master" would do, fetching
"master" from "origin" and merging it to the commit you have checked
out.
Your "git checkout master && git pull" does something else. It uses the
configured pull defaults for "master" to fetch something and merge it to
"master".
> Also, is "branch..remote" valid? Should this be "branch.remote"?
That's a bug, but it should not be branch.remote. The config setting is
branch.<name>.remote. As you were on a detached HEAD, there is no
"<name>", and the code that generates the error message doesn't handle
that correctly. I'd even say that in this case, the whole "If you often
merge ..." part makes no sense at all, you simply can't setup pull
defaults for a detached HEAD.
> + echo "You may not be on a branch. In this case, you need to move"
> + echo "onto the branch you want to pull to (usually master):"
Hm? Neither do you really need to move to a branch, nor is "master"
really _that_ special that it is warranted to recommend checking it
out... IMHO.
Björn
next prev parent reply other threads:[~2009-04-05 22:10 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-05 21:33 Running 'git pull' from an unnamed branch Reece Dunn
2009-04-05 21:37 ` Sverre Rabbelier
2009-04-05 21:42 ` Markus Heidelberg
2009-04-05 22:15 ` Reece Dunn
2009-04-05 22:28 ` Markus Heidelberg
2009-04-05 22:08 ` Björn Steinbrink [this message]
2009-04-05 22:29 ` Reece Dunn
2009-04-06 1:05 ` Junio C Hamano
2009-04-06 7:42 ` Reece Dunn
2009-04-06 10:03 ` Björn Steinbrink
2009-04-06 12:04 ` Reece Dunn
2009-04-06 21:05 ` Markus Heidelberg
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=20090405220855.GA20356@atjola.homenet \
--to=b.steinbrink@gmx.de \
--cc=git@vger.kernel.org \
--cc=msclrhd@googlemail.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).