From: Kevin Green <kevin.t.green@morganstanley.com>
Date: Fri, 15 Jun 2007 15:40:00 GMT
Subject: Re: [RFC][PATCH] Fix assumption that git is installed in a standard place on the remote end ssh
Message-ID: <20070615154000.GK14677@menevado.ms.com>
In-Reply-To: <Pine.LNX.4.64.0706151628180.31972@reaper.quantumfyre.co.uk>

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