The problem seems to be that the Git process on the remote end has a
current working directory that it doesn't think is a Git reponsitory.

Most likely this is because the Git remote link has directed the
remote process to be in a directory that *isn't* a Git repository.  Is
there any way that you can verify what the remote directory is?  Also,
what actually is in that directory?  Have you verified that everything
in that directory is readable/writable by the UID under which the
remote Git is executing?

What is the remote link that the near-end Git is using to perform the

One thing I notice in an early message is that the "ls -la" shows:

    remote: total 12
    remote: drwxr-xr-x  3 git  git  4096 26. Jul 16:12 .
    remote: drwxrwxrwt. 4 root root 4096 26. Jul 16:08 ..
    remote: drwxrwxr-x  8 git  git  4096 26. Jul 16:12 .git

This suggests that the current working directory is not the .git
directory, but the woking copy directory that contains it.  I don't
know the official specification (and it's not likely to have been
written down anywhere), but it is possible that the directory for
remote operations *must* be a *bare* repository.  Try adding a "/.git"
to the end of the remote URL for the remote link.


You received this message because you are subscribed to the Google Groups "Git 
for human beings" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
For more options, visit

Reply via email to