From: Andy Parkins <andyparkins@gmail.com>
To: git@vger.kernel.org
Subject: git-fetch while on "(no branch)"
Date: Mon, 15 Jan 2007 10:09:50 +0000 [thread overview]
Message-ID: <200701151009.51868.andyparkins@gmail.com> (raw)
Hello,
Just ran this while on a detached HEAD.
$ git fetch
fatal: ref HEAD is not a symbolic ref
fatal: ref HEAD is not a symbolic ref
fatal: ref HEAD is not a symbolic ref
remote: Generating pack...
...etc...
The fetch appears to have succeeded anyway, but it's a scary message that
tells a user something is "fatal". Has this done any damage?
Andy
--
Dr Andy Parkins, M Eng (hons), MIEE
andyparkins@gmail.com
next reply other threads:[~2007-01-15 17:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-15 10:09 Andy Parkins [this message]
2007-01-15 21:24 ` [PATCH] git-{parse-remote,pull}: throw away stderr of git-symbolic-ref Jeff King
2007-01-15 22:07 ` Junio C Hamano
2007-01-15 22:25 ` [PATCH] git-pull: disallow implicit merging to detached HEAD Jeff King
2007-01-15 22:28 ` Jeff King
2007-01-15 21:56 ` git-fetch while on "(no branch)" Junio C Hamano
2007-01-15 22:01 ` Jeff King
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=200701151009.51868.andyparkins@gmail.com \
--to=andyparkins@gmail.com \
--cc=git@vger.kernel.org \
/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).