On Thu, 30 Jul 2009 12:00:29 -0500 Jeffrey Middleton <jefromi@xxxxxxxxx> wrote: > I'm wondering about the intended behavior of the > --exec-path/GIT_EXEC_PATH option - is it supposed to override or add > to the built-in path? It seems to do some of both. [...] > There are plenty of commands in each category, and it's not > immediately obvious to me what criteria separate them. Not a huge > problem, since it's easy enough to use --exec-path=foo:<normal-path>, > but I was in the process of adding support for exec-path to the bash > completion, and it's an important distinction there - and much easier > if it adds to the built-in, of course. Jeffrey, The commands that are "built-in" and compiled into the git executable will execute because no searching of the exec-path is necessary. Any commands that are compiled into a separate executable will fail since git can not find them in the incorrect exec-path directory. If you take a listing of the exec-path directory on your system you'll see that many commands are hard-linked to the single "git" executable. The commands that aren't linked to git are external and will be those that fail when you supply an erroneous exec-path. Sean -- To unsubscribe from this list: 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