From: "Shawn O. Pearce" <spearce@spearce.org>
To: Scott Parish <sRp@srparish.net>
Cc: git@vger.kernel.org
Subject: Re: intended use of "git --exec-path"?
Date: Wed, 24 Oct 2007 00:38:19 -0400 [thread overview]
Message-ID: <20071024043819.GI14735@spearce.org> (raw)
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.
next prev parent reply other threads:[~2007-10-24 4:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-24 4:32 intended use of "git --exec-path"? Scott Parish
2007-10-24 4:38 ` Shawn O. Pearce [this message]
2007-10-24 5:47 ` Scott Parish
2007-10-24 5:54 ` David Symonds
2007-10-24 8:08 ` Andreas Ericsson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20071024043819.GI14735@spearce.org \
--to=spearce@spearce.org \
--cc=git@vger.kernel.org \
--cc=sRp@srparish.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).