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

Re: Problem upgrading to 1.4.0

From
Junio C Hamano <junkio@cox.net>
Date
Jun 11, 2006, 02:12 UTC
Message-ID
<7v1wtwh246.fsf@assigned-by-dhcp.cox.net>
In-Reply-To
<93c3eada0606101707t5eb35a4du3ebd0fd17737943f@mail.gmail.com>
"Geoff Russell" <geoffrey.russell@gmail.com> writes:
Show 14 quoted lines
> Hi,
>
> When I do a "git pull origin" I get messages:
>
>             error: no such remote ref refs/heads/gb/diffdelta
>             error: no such remote ref refs/heads/jc/bind
>             error: no such remote ref refs/heads/jc/bind-2
>             ...
>             Fetch failure: git://git.kernel.org/pub/scm/git/git.git
>...
> So I went into .git/remotes/origin and
> removed the lines pointing at these branches and removed the gb and jc
> directories
> and did another git pull and it seems to have worked.

This is the second time this same gotcha caused trouble here. I agree it would be sensible to make git-fetch (which is called by git-pull) to detect stale entries in the remotes/origin file and remote.origin.fetch configuration items.

Previous: Geoff RussellNext: Pavel Roskin
Message 2 of 8 in “Problem upgrading to 1.4.0”
  1. Geoff RussellJun 11, 2006
  2. Junio C HamanoJun 11, 2006
  3. Pavel RoskinJun 13, 2006
  4. SeanJun 13, 2006
  5. Pavel RoskinJun 13, 2006
  6. Linus TorvaldsJun 13, 2006
  7. Pavel RoskinJun 13, 2006
  8. Geoff RussellJun 13, 2006

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.