{"thread":{"id":"24230","subject":"Confusing error message from \"git pull\" when upstream repo no longer exists","startedAt":"2010-06-29T10:33:16Z","lastAt":"2010-06-29T11:14:37Z","messageCount":3,"participants":["Per Cederqvist","Santi Béjar"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"144453","messageId":"op.ve14xqlq0i1pst@centurion","threadId":"24230","inReplyTo":null,"subject":"Confusing error message from \"git pull\" when upstream repo no longer exists","fromName":"Per Cederqvist","fromEmail":"cederp@opera.com","sentAt":"2010-06-29T10:33:16Z","receivedAt":"2010-06-29T10:33:16Z","isPatch":false,"sender":{"key":"cederp@opera.com","avatar":"https://gravatar.com/avatar/008fe28caedea0ba34042cd5157705267934f4ba7a9b29fb248ae18ec5b3055e?d=mp&s=160"},"body":"When running \"git pull\", I get this error message:\n\n     fatal: /usr/local/libexec/git-core/git-pull cannot be used without a  \nworking tree.\n\n\"git fetch\" gives me a much clearer error message:\n\n     fatal: '/var/git/project.git' does not appear to be a git repository\n     fatal: The remote end hung up unexpectedly\n\n/var/git/project.git does no longer exist on the origin server, so I\nunderstand why the commands fail.  I think \"git pull\" should have a\nless confusing error message, though.\n\n     /ceder\n-- \nPer Cederqvist, cederp@opera.com\n"},{"id":"144454","messageId":"AANLkTilbqmedF9Wh3dG3n9HYtuZuq4PzTwOp6T8NCjQ8@mail.gmail.com","threadId":"24230","inReplyTo":"op.ve14xqlq0i1pst@centurion","subject":"Re: Confusing error message from \"git pull\" when upstream repo no longer exists","fromName":"Santi Béjar","fromEmail":"santi@agolina.net","sentAt":"2010-06-29T10:55:29Z","receivedAt":"2010-06-29T10:55:29Z","isPatch":false,"sender":{"key":"santi@agolina.net","avatar":null},"body":"On Tue, Jun 29, 2010 at 12:33 PM, Per Cederqvist <cederp@opera.com> wrote:\n> When running \"git pull\", I get this error message:\n>\n>    fatal: /usr/local/libexec/git-core/git-pull cannot be used without a\n> working tree.\n\nThis error message is shown when you try to pull in a bare repository\n(without a working tree). It seems you don't have a working tree, but\nyou have a repository, so you can still fetch. (the working tree check\nis done before the fetch).\n\nHTH,\nSanti\n"},{"id":"144455","messageId":"op.ve16un100i1pst@centurion","threadId":"24230","inReplyTo":"AANLkTilbqmedF9Wh3dG3n9HYtuZuq4PzTwOp6T8NCjQ8@mail.gmail.com","subject":"Re: Confusing error message from \"git pull\" when upstream repo no longer exists","fromName":"Per Cederqvist","fromEmail":"cederp@opera.com","sentAt":"2010-06-29T11:14:37Z","receivedAt":"2010-06-29T11:14:37Z","isPatch":false,"sender":{"key":"cederp@opera.com","avatar":"https://gravatar.com/avatar/008fe28caedea0ba34042cd5157705267934f4ba7a9b29fb248ae18ec5b3055e?d=mp&s=160"},"body":"On Tue, 29 Jun 2010 12:55:29 +0200, Santi Béjar <santi@agolina.net> wrote:\n\n> On Tue, Jun 29, 2010 at 12:33 PM, Per Cederqvist <cederp@opera.com>  \n> wrote:\n>> When running \"git pull\", I get this error message:\n>>\n>>    fatal: /usr/local/libexec/git-core/git-pull cannot be used without a\n>> working tree.\n>\n> This error message is shown when you try to pull in a bare repository\n> (without a working tree). It seems you don't have a working tree, but\n> you have a repository, so you can still fetch. (the working tree check\n> is done before the fetch).\n>\n> HTH,\n> Santi\n\nOh. You are correct. I was in a bare repository, so I guess the message\nis good after all. Sorry for my mistaken report.\n\n     /ceder\n-- \nPer Cederqvist, cederp@opera.com\n"}]}