Re: Teach the "git" command to handle some commands internally

From: Junio C Hamano <junkio@cox.net>
Date: Feb 26, 2006, 23:46 UTC
Message-ID: <7vy7zx65v0.fsf@assigned-by-dhcp.cox.net>
In-Reply-To: <Pine.LNX.4.64.0602261518110.22647@g5.osdl.org>

Linus Torvalds <torvalds@osdl.org> writes:

Show 12 quoted lines

> On Sun, 26 Feb 2006, Junio C Hamano wrote:
>> 
>> > There's one other change: the search order for external programs is 
>> > modified slightly, so that the first entry remains GIT_EXEC_DIR, but the 
>> > second entry is the same directory as the git wrapper itself was executed 
>> > out of - if we can figure it out from argv[0], of course.
>> 
>> I am not sure about this part, though.
>
> Well, what it means is that _if_ you install all your "git" binaries in 
> some directory that is not in your patch and is not GIT_EXEC_DIR, they 
> will still magically work, assuming you don't do something strange.

I understood that part. I was wondering if this change defeats what Michal (you sensibly CC'ed your message to) wanted to do earlier, going great length trying to avoid mucking with PATH and "where-ever git itself is found" in the last round. After reviewing the change in 77cb17 commit, I realize my worry was unfounded.