{"thread":{"id":"20299","subject":"exec-path behavior","startedAt":"2009-07-30T17:00:29Z","lastAt":"2009-07-30T17:48:01Z","messageCount":2,"participants":["Jeffrey Middleton","Sean Estabrooks"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"119179","messageId":"4389ce950907301000m5b264771jf87cc06398bee7e0@mail.gmail.com","threadId":"20299","inReplyTo":null,"subject":"exec-path behavior","fromName":"Jeffrey Middleton","fromEmail":"jefromi@gmail.com","sentAt":"2009-07-30T17:00:29Z","receivedAt":"2009-07-30T17:00:29Z","isPatch":false,"sender":{"key":"jefromi@gmail.com","avatar":null},"body":"I'm wondering about the intended behavior of the\n--exec-path/GIT_EXEC_PATH option - is it supposed to override or add\nto the built-in path?  It seems to do some of both.\n\n$ git --exec-path=foo rebase\ngit: 'rebase' is not a git-command. See 'git --help'.\n\nbut:\n\n$ git --exec-path=foo status\n# On branch master\nnothing to commit (working directory clean)\n\nThere are plenty of commands in each category, and it's not\nimmediately obvious to me what criteria separate them.  Not a huge\nproblem, since it's easy enough to use --exec-path=foo:<normal-path>,\nbut I was in the process of adding support for exec-path to the bash\ncompletion, and it's an important distinction there - and much easier\nif it adds to the built-in, of course.\n\n\nThanks,\nJeffrey\n"},{"id":"119183","messageId":"BLU0-SMTP449412ED39DA595CF1527AAE130@phx.gbl","threadId":"20299","inReplyTo":"4389ce950907301000m5b264771jf87cc06398bee7e0@mail.gmail.com","subject":"Re: exec-path behavior","fromName":"Sean Estabrooks","fromEmail":"seanlkml@sympatico.ca","sentAt":"2009-07-30T17:48:01Z","receivedAt":"2009-07-30T17:48:01Z","isPatch":false,"sender":{"key":"seanlkml@sympatico.ca","avatar":"https://gravatar.com/avatar/f92923f54fc08c401fc59b71829d4b89e9b8087fbba45ff87c82e6a83aee02ae?d=mp&s=160"},"body":"On Thu, 30 Jul 2009 12:00:29 -0500\nJeffrey Middleton <jefromi@gmail.com> wrote:\n\n> I'm wondering about the intended behavior of the\n> --exec-path/GIT_EXEC_PATH option - is it supposed to override or add\n> to the built-in path?  It seems to do some of both.\n[...]\n> There are plenty of commands in each category, and it's not\n> immediately obvious to me what criteria separate them.  Not a huge\n> problem, since it's easy enough to use --exec-path=foo:<normal-path>,\n> but I was in the process of adding support for exec-path to the bash\n> completion, and it's an important distinction there - and much easier\n> if it adds to the built-in, of course.\n\nJeffrey,\n\nThe commands that are \"built-in\" and compiled into the git executable\nwill execute because no searching of the exec-path is necessary.  Any\ncommands that are compiled into a separate executable will fail since\ngit can not find them in the incorrect exec-path directory.\n\nIf you take a listing of the exec-path directory on your system you'll\nsee that many commands are hard-linked to the single \"git\" executable.\nThe commands that aren't linked to git are external and will be those\nthat fail when you supply an erroneous exec-path.\n\nSean\n"}]}