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

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Linus Torvalds <torvalds@xxxxxxxx> writes:

> 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.

-
: 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

[Index of Archives]     [Linux Kernel Development]     [Gcc Help]     [IETF Annouce]     [DCCP]     [Netdev]     [Networking]     [Security]     [V4L]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux SCSI]     [Fedora Users]