Re: [ANNOUNCE] GIT 1.6.0-rc2

From: David Miller <davem@davemloft.net>
Date: Sep 15, 2008, 18:25 UTC
Message-ID: <20080915.112545.193713350.davem@davemloft.net>
In-Reply-To: <20080915171240.GB4787@efreet.light.src>

From: Jan Hudec <bulb@ucw.cz>
Date: Mon, 15 Sep 2008 19:12:40 +0200

Show 9 quoted lines

> On Sat, Sep 13, 2008 at 01:33:30 -0700, David Miller wrote:
> > Wouldn't it make sense to put the bindir into PATH when we try to do
> > execv_git_cmd()?  The code has already put the gitexecdir into the
> > PATH at this point.
> 
> I don't think it gets to execv_git_cmd(). Git on local side will run
>     ssh <host> git upload-pack
> and it's ssh that can't find git in ~/bin (or maybe it's still using the
> dashed form for backward compatibility; the argument stands either way).

That's not the case I'm running into. The initial GIT execution works, it's when GIT forks up sub processes and tries to execute other things that problem show up.

I added tracing and on the ssh remote system, and my PATH had the GIT exec dir in my path when the problem triggers.