Hi,
On Wed, 30 Jul 2008, Steve Haslam wrote:
I think that once git-upload-pack.c et al get the argv[0] path over to
setup_path() then there's nothing more to do; setup_path() already uses
argv0_path in its list of paths to try. I'm confused to the reference to
PATH, though: we're avoiding the PATH environment variable completely.
There is an issue in setting up the argv0_path when Git is called as "git"
and resolved via the PATH: argv[0] then is literally "git".
And we need argv0_path for other things than just calling programs:
relative etc/gitconfig and libexecdir.
Ciao,
Dscho