Thanks to anyone for the reply, but this issue has been resolved. I might have submitted this several times, but Nabble keeps on nagging me about multiple posts. So I'm just going to delete it. -----Original Message----- From: Daniel Barkalow [mailto:barkalow@xxxxxxxxxxxx] Sent: 20 October 2009 17:34 To: Richard Cc: git@xxxxxxxxxxxxxxx Subject: Re: Moving git On Tue, 20 Oct 2009, Richard Lee wrote: > > Hi Git forum, > > I've just started using git yesterday, so I'm very new. So please excuse if > I've done something the wrong way. > > I cloned a git directory/repository? and then moved it. I'm trying to prune > branches and it gives > > ]fatal: '/var/www/vhosts/mydomain.co.uk/b2.git': unable to chdir or not a > git archive > fatal: The remote end hung up unexpectedly > ls-remote --heads /var/www/vhosts/mydomain.co.uk/b2.git: command returned > error: 1 > > b2.git was the cloned bare thing I create following the instruction here: > > http://book.git-scm.com/4_setting_up_a_private_repository.html > > Is there someway I can get git to update the git base directory? The exact problem, I think, is that your clone has saved the original location of the bare repository as the default upstream repository location, and now it's not there. (It's a little hard to tell without the command that you were running when you got the error.) If you edit the clone's .git/config, you should see the old location in a '[remote "origin"]' section. If you change this to the new location, everything should work. You can also do it with "git remote" somehow, but I personally just edit the config file, so I don't know the details. -Daniel *This .sig left intentionally blank* -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html