On Thu, 16 Mar 2006 14:34:42 +0000 (GMT) Paul Jakma <paul@xxxxxxxx> wrote: > If a git repository has a reset HEAD~X done, then any later pulls in > clone repositories get /really/ upset, with: > > $ git pull > * refs/heads/origin: does not fast forward to branch 'master' of > /home/paul/foo-git/; > > Type of thing. This seems to be a similar issue to: > > http://www.gelato.unsw.edu.au/archives/git/0510/10767.html > > The question is has this improved at all since last year? Is there > anything the origin repository maintainer (the one who did reset) can > do to recover from this? It's still not a recommended operation on a repository that is pulled by others. If you realize you made a mistake by resetting the head, you can undo the operation afterward with: $ git reset ORIG_HEAD Sean - : 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