On 06/15/07 11:30:12, Julian Phillips wrote: > On Fri, 15 Jun 2007, Kevin Green wrote: > > > > > Hi, > > > > I've run into a problem pushing/pulling where we don't (READ: can't) have git installed in the > > standard location. This leads to a failure on trying to find the git binaries > > on the remote end. I've looked through the archives and didn't come across > > any similar discussions. Please point me there if I've missed something... > > from the git-pull manpage: > > --upload-pack <upload-pack> > When given, and the repository to fetch from is handled by > git-fetch-pack, --exec=<upload-pack> is passed to the command > to specify non-default path for the command run on the other > end. > > and git-pull: > > --receive-pack=<git-receive-pack> > Path to the git-receive-pack program on the remote end. > Sometimes useful when pushing to a remote repository over ssh, > and you do not have the program in a directory on the default > $PATH. Thanks! I did completely miss this when I went through the manpage... I'm thinking I like the env var idea much more though. I can just export it in my shell and it works in both cases. I could of course alias the commands so I don't have to keep typing it everytime, but that's more painful still... --Kevin - 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
