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

Re: Errors when updating an old git.git repository

From
Johannes Schindelin <johannes.schindelin@gmx.de>
Date
Dec 26, 2006, 22:54 UTC
Message-ID
<Pine.LNX.4.63.0612262350070.19693@wbgn013.biozentrum.uni-wuerzburg.de>
In-Reply-To
<87ac1awjh0.fsf@trews52.bothi.fi>
Hi,
On Tue, 26 Dec 2006, Hannu Koivisto wrote:
Show 11 quoted lines
> "Lars Hjemli" <hjemli@gmail.com> writes:
> 
> > On 12/26/06, Hannu Koivisto <azure@iki.fi> wrote:
> 
> > 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.
> 
> Thanks, but I don't need to fix the repository since a clean clone 
> works, I just wanted to report it so that git can be fixed, if possible.
Git works quite as expected here, so there is nothing to fix.
> 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

Since you said it is an older git repository, I guess that in your .git/remotes/origin are some lines like this:

	Pull: refs/heads/jc/bind:refs/heads/jc/bind

So, you _asked_ git to fetch these three branches! By not providing _any_ remote, you said: "look into .git/remotes/origin". And in that file you said: "fetch bind, bind-2 and diffdelta".

And git faithfully reports that it cannot fetch these branches (they are no longer there) and errors out.

Ciao, Dscho

Previous: Hannu KoivistoNext: Junio C Hamano
Message 4 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.