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

Re: intended use of "git --exec-path"?

From
Shawn O. Pearce <spearce@spearce.org>
Date
Oct 24, 2007, 04:38 UTC
Message-ID
<20071024043819.GI14735@spearce.org>
In-Reply-To
<20071024043224.GR16291@srparish.net>
Scott Parish <sRp@srparish.net> wrote:
> "git --exec-path" presently prints out the highest priority path
> to find executable in. That's a what; i'm curious why and when it
> should be used. Basically i'm wondering if its still useful, and
> what, if anything, it should be printing.

git-gui uses it. git-gui runs git-* by prefixing it with the exec path. It also scans the first line of the file if we are on Windows and the "executable" doesn't end in ".exe" so it can figure out what process to run it through.

So it really can't go away.
-- 
Shawn.
Previous: Scott ParishNext: Scott Parish
Message 2 of 5 in “intended use of "git --exec-path"?”
  1. Scott ParishOct 24, 2007
  2. Shawn O. PearceOct 24, 2007
  3. Scott ParishOct 24, 2007
  4. David SymondsOct 24, 2007
  5. Andreas EricssonOct 24, 2007

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.