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

bug related to branches using / in name

From
STSimon Holm Thøgersen <odie@cs.aau.dk>
Date
Jun 26, 2008, 19:42 UTC
Message-ID
<1214509350.28344.31.camel@odie.local>
Hi git community

I have a bug report I think is most easily explained by a list of commands that illustrates the bug.

cd /tmp mkdir git-bug cd git-bug git init touch foo git add foo git commit -a -m '...' git branch sched git clone file:///tmp/git-bug /tmp/git-bug-clone git branch -d sched git branch sched/urgent git branch sched/devel cd /tmp/git-bug-clone git pull

The last command does not succeed, but produces the following output

error: unable to resolve reference refs/remotes/origin/sched/devel: Not a directory

>From file:///tmp/git-bug
 * [new branch]      sched/devel -> origin/sched/devel
error: unable to resolve reference refs/remotes/origin/sched/urgent: Not
a directory
 * [new branch]      sched/urgent -> origin/sched/urgent

I can work around it by rm /tmp/git-bug-clone/.git/{,logs/}refs/remotes/origin/sched

but git should take care of this automatically, right?
I'm on git version 1.5.6.
Simon Holm Thøgersen
Next: Jeff King
Message 1 of 13 in “bug related to branches using / in name”
  1. Simon Holm ThøgersenJun 26, 2008
  2. Jeff KingJun 27, 2008
  3. Jeff KingJun 27, 2008
  4. Simon Holm ThøgersenJun 27, 2008
  5. Jeff KingJun 27, 2008
  6. fetch: report local storage errors in status tableJeff King, Jun 27, 2008
  7. Junio C HamanoJun 27, 2008
  8. Jeff KingJun 28, 2008
  9. 2/2 fetch: give a hint to the user when local refs fail to updateJeff King, Jun 27, 2008
  10. Junio C HamanoJun 27, 2008
  11. Jeff KingJun 28, 2008
  12. Junio C HamanoJun 28, 2008
  13. Jakub NarebskiJun 28, 2008

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.