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

Sometimes "Failed to find remote refs" means "try git-fetch --no-tags"

From
MEMichael K. Edwards <medwards.linux@gmail.com>
Date
Nov 15, 2006, 03:53 UTC
Message-ID
<f2b55d220611141953t48d81ac5q4f48183ae79ba0a@mail.gmail.com>
Down inside git-ls-remote there is a die "Failed to find remote refs".
 This struck when I tried to fetch an http repository with a missing
info/refs file.  Using "git fetch --no-tags" succeeds because it
doesn't have to call git-ls-remote at all.  Does git-ls-remote have
any way of knowing who is calling it so that it can print a
context-appropriate error message?  If not, is it worth adding some
sort of "caller context" mechanism, perhaps at the boundary between
porcelain and plumbing?  Or should the error message include, "If you
were trying to do a 'git fetch', try --no-tags; you won't get tags but
you may get a good update of the branch content"?
Cheers,
Next: Junio C Hamano
Message 1 of 2 in “Sometimes "Failed to find remote refs" means "try git-fetch --no-tags"”
  1. Michael K. EdwardsNov 15, 2006
  2. Junio C HamanoNov 15, 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.