From: Mike Hommey <mh@glandium.org>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: Scott Parish <sRp@srparish.net>,
Johannes Sixt <j.sixt@viscovery.net>,
git@vger.kernel.org
Subject: Re: [PATCH] allow git to use the PATH for finding subcommands and help docs
Date: Fri, 19 Oct 2007 18:48:16 +0200 [thread overview]
Message-ID: <20071019164816.GA24573@glandium.org> (raw)
In-Reply-To: <Pine.LNX.4.64.0710191616490.16728@wbgn129.biozentrum.uni-wuerzburg.de>
On Fri, Oct 19, 2007 at 04:27:39PM +0200, Johannes Schindelin wrote:
> While reading this, I have to wonder why it is not just simpler to try
> with builtin_exec_path first, and if that fails, just let exec() find the
> program in the PATH?
Why not try the directory where the git executable is, too ?
Mike
next prev parent reply other threads:[~2007-10-19 16:50 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-19 6:59 [PATCH] allow git to use the PATH for finding subcommands and help docs Scott R Parish
2007-10-19 7:33 ` Johannes Sixt
2007-10-19 13:04 ` Scott Parish
2007-10-19 13:21 ` Johannes Sixt
2007-10-19 14:18 ` Scott Parish
2007-10-19 14:34 ` Johannes Sixt
2007-10-19 14:27 ` Johannes Schindelin
2007-10-19 16:48 ` Mike Hommey [this message]
2007-10-19 17:19 ` Johannes Schindelin
2007-10-20 6:42 ` Scott Parish
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=20071019164816.GA24573@glandium.org \
--to=mh@glandium.org \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=j.sixt@viscovery.net \
--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).