On Wednesday, October 10, 2012 7:13:09 PM UTC+2, Yaron Kaplan wrote:
> I've been using Eclipse with eGit and it works fairly well.
> However, my boss has Zend Studio. Today we tried committing from it (from
> a repository we cloned into Zend Studio) and 3 things happened:
> 1. It said it committed, but still marked the repository with outgoing
> 2. The commits did not appear on the remote repository,
> 3. The repository became unusable after that. Any attempt to pull / clone
> that repository resulted in horrifying error messages such as this:
> error: refs/remotes/origin/master does not point to a valid object!
> error: Trying to write ref refs/heads/master with nonexistant object
> fatal: Cannot update the ref 'HEAD'.
> The remote repository is stored at unfuddle.com
> Now I have to erase all those repositories and re-create them. very
> annoying. Can't think of another way to solve this.
> So.. what should I do? Should I report this to anyone?
I think there are some known issues in older versions of EGit/JGit that
cause this. Github describes an approach for fixing it here:
You should be able to follow a similar approach with unfuddle, only the
parts with the admin page are different, I suppose.
What I imagine is going on is that your boss' Git client is updating the
remote master to point at his latest commit (update-ref), but fails to
actually push the commit being referred to (a bug in his EGit). So what you
need to do is basically an update-ref in the remote repository to point
master at the correct commit again, but since there is no way to do this
(update-ref has to be done directly on the repository from "localhost") you
have to do it by re-creating the branch. If that makes any sense.
You received this message because you are subscribed to the Google Groups "Git
for human beings" group.
To view this discussion on the web visit
To post to this group, send email to email@example.com.
To unsubscribe from this group, send email to
For more options, visit this group at