git/list[1] front-page[2] threads[3] people[4] search[5] about
 

exec-path behavior

From
JMJeffrey Middleton <jefromi@gmail.com>
Date
Jul 30, 2009, 17:00 UTC
Message-ID
<4389ce950907301000m5b264771jf87cc06398bee7e0@mail.gmail.com>

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.

$ git --exec-path=foo rebase git: 'rebase' is not a git-command. See 'git --help'.

but:

$ git --exec-path=foo status # On branch master nothing to commit (working directory clean)

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.

Thanks, Jeffrey

Next: Sean Estabrooks
Message 1 of 2 in “exec-path behavior”
  1. Jeffrey MiddletonJul 30, 2009
  2. Sean EstabrooksJul 30, 2009

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.