On Thu, 2007-06-21 at 21:24 -0500, Andrew Ruder wrote: > On Thu, Jun 21, 2007 at 07:00:18PM -0700, Junio C Hamano wrote: > > $ ssh newberry.ihepa.ufl.edu sh -c 'echo $PATH' > > > > may be a good starting point to test this, and the first step > > to fix it would be > > > > $ man ssh > > $ man sshd > > While I wholeheartedly agree with Junio here, you may also find > > remote.<name>.receivepack Yes, but it doesn't always work. I have a server with several repositories, and git is installed in /usr/local/bin. All my local repostories know this server as a remote named 'slcom' and I have a 2 global options remote.slcom.uploadpack=/usr/local/bin/git-upload-pack remote.slcom.receivepack=/usr/local/bin/git-receive-pack Fetching, pulling and normal pushing works. Pushing a new branch to the remote doesn't work: $ git branch test $ git push slcom test:test error: dst refspec test does not match any existing ref on the remote and does not start with refs/. fatal: The remote end hung up unexpectedly error: failed to push to 'ray@xxxxxxxxxxxxxxxxxxxxxx:/home/ray/repos/drupal/multirate' git-remote also has a problem: $ git remote show slcom bash: git-upload-pack: command not found fatal: The remote end hung up unexpectedly ls-remote --heads ray@xxxxxxxxxxxxxxxxxxxxxx:/home/ray/repos/drupal/multirate: command returned error: 1 All this with git from yesterday (next). > - Andy -- best regards Ray - 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
