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

Confusing error message from "git pull" when upstream repo no longer exists

From
Per Cederqvist <cederp@opera.com>
Date
Jun 29, 2010, 10:33 UTC
Message-ID
<op.ve14xqlq0i1pst@centurion>
When running "git pull", I get this error message:
     fatal: /usr/local/libexec/git-core/git-pull cannot be used without a  
working tree.
"git fetch" gives me a much clearer error message:
     fatal: '/var/git/project.git' does not appear to be a git repository
     fatal: The remote end hung up unexpectedly

/var/git/project.git does no longer exist on the origin server, so I understand why the commands fail. I think "git pull" should have a less confusing error message, though.

     /ceder
-- 
Per Cederqvist, cederp@opera.com
Next: Santi Béjar
Message 1 of 3 in “Confusing error message from "git pull" when upstream repo no longer exists”
  1. Per CederqvistJun 29, 2010
  2. Santi BéjarJun 29, 2010
  3. Per CederqvistJun 29, 2010

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.