git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Remote branch can not be resolved as commit?

From
KSKendall Shaw <kshaw@kendallshaw.com>
Date
May 22, 2013, 14:29 UTC
Message-ID
<519CD63A.20802@kendallshaw.com>

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: Holger Hellmuth (IKS)
Message 1 of 2 in “Remote branch can not be resolved as commit?”
  1. Kendall ShawMay 22, 2013
  2. Holger Hellmuth (IKS)May 23, 2013

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.