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

Re: Errors when updating an old git.git repository

From
LHLars Hjemli <hjemli@gmail.com>
Date
Dec 26, 2006, 15:37 UTC
Message-ID
<8c5c35580612260737vae2669dkac6a81fe863484d4@mail.gmail.com>
In-Reply-To
<87d566ww3r.fsf@trews52.bothi.fi>
On 12/26/06, Hannu Koivisto <azure@iki.fi> wrote:
> error: no such remote ref refs/heads/jc/bind
> error: no such remote ref refs/heads/jc/bind-2
> error: no such remote ref refs/heads/gb/diffdelta

I guess you have some branch references in the file .git/remotes/origin that shouldn't be there, so you can just remove the lines that mention 'jc/bind', 'jc/bind-2' and 'gb/diffdelta' from that file.

> * refs/heads/pu: not updating to non-fast forward branch 'pu' of git://git.kernel.org/pub/scm/git/git
>   old...new: 0c9951a...f959571

The pu branch is rebased all the time so it needs a '+' in .git/remotes/origin to be automatically updated, like this:

Pull: +pu:pu
(or you can run 'git pull -f' to force the update)
-- 
larsh
Previous: Hannu KoivistoNext: Hannu Koivisto
Message 2 of 7 in “Errors when updating an old git.git repository”
  1. Hannu KoivistoDec 26, 2006
  2. Lars HjemliDec 26, 2006
  3. Hannu KoivistoDec 26, 2006
  4. Johannes SchindelinDec 26, 2006
  5. Junio C HamanoDec 27, 2006
  6. Hannu KoivistoDec 27, 2006
  7. Junio C HamanoDec 27, 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.