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

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

From
SBSanti Béjar <santi@agolina.net>
Date
Jun 29, 2010, 10:55 UTC
Message-ID
<AANLkTilbqmedF9Wh3dG3n9HYtuZuq4PzTwOp6T8NCjQ8@mail.gmail.com>
In-Reply-To
<op.ve14xqlq0i1pst@centurion>
On Tue, Jun 29, 2010 at 12:33 PM, Per Cederqvist <cederp@opera.com> wrote:
> When running "git pull", I get this error message:
>
>    fatal: /usr/local/libexec/git-core/git-pull cannot be used without a
> working tree.

This error message is shown when you try to pull in a bare repository (without a working tree). It seems you don't have a working tree, but you have a repository, so you can still fetch. (the working tree check is done before the fetch).

HTH, Santi

Previous: Per CederqvistNext: Per Cederqvist
Message 2 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.