From: Kendall Shaw <kshaw@kendallshaw.com>
To: git@vger.kernel.org
Subject: Remote branch can not be resolved as commit?
Date: Wed, 22 May 2013 07:29:14 -0700 [thread overview]
Message-ID: <519CD63A.20802@kendallshaw.com> (raw)
I am trying to setup a repository for use inside the LAN, but I have
been unable to checkout any branch so far. I am very new to git.
The repository is being served from gitblit over https. I have
GIT_SSL_NO_VERIFY=true. The repository was created from git svn.
git ls-remote
shows the remote branches, e.g.:
... refs/remotes/2.0.3
... refs/remotes/trunk
git branch -r
shows none of the remote branches.
git checkout -b new-2.0.3 origin/2.0.3
produces:
fatal: git checkout: updating paths is incompatible with switching branches.
Did you intend to checkout 'origin/2.0.3' which can not be resolved as
commit?
What does that mean?
I get the same result after each of these:
git fetch
git remote update
git fetch
git add remote stage-repo https://example.com:8443/git/blah-tools.git
git fetch stage-repo
git checkout -b new-2.0.3 stage-repo/2.0.3
Can you explain what the error message means, and what I am doing wrong?
Kendall
next reply other threads:[~2013-05-22 15:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-22 14:29 Kendall Shaw [this message]
2013-05-23 8:45 ` Remote branch can not be resolved as commit? Holger Hellmuth (IKS)
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=519CD63A.20802@kendallshaw.com \
--to=kshaw@kendallshaw.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).