From: Alex Riesen <raa.lkml@gmail.com>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: git@vger.kernel.org
Subject: Re: how about removing --exec-path?
Date: Sat, 26 Jul 2008 08:48:31 +0200 [thread overview]
Message-ID: <20080726064831.GA3698@blimp.local> (raw)
In-Reply-To: <alpine.DEB.1.00.0807260448210.26810@eeepc-johanness>
Johannes Schindelin, Sat, Jul 26, 2008 04:49:06 +0200:
> On Fri, 25 Jul 2008, Alex Riesen wrote:
>
> > The thing has at least this problem: is not passed to upload-pack when
> > running fetch.
>
> It should be added to PATH, and so it is passed to upload-pack, amongst
> others, in a sense.
>
Yes, but next time upload-pack runs a program, it adds builtin exec
path to PATH (because --exec-path not given to transport's uploadpack
command). So it looks like this:
$GIT_EXEC_PATH:/usr/local/libexec/git-core:/orig/exec-path:\
$GIT_EXEC_PATH:/usr/local/libexec/git-core:$ORIG_USER_PATH
which kind of useless for debugging. So using GIT_EXEC_PATH is the
only way (and why did we need more? Working around something?)
prev parent reply other threads:[~2008-07-26 7:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-25 9:40 how about removing --exec-path? Alex Riesen
2008-07-26 2:49 ` Johannes Schindelin
2008-07-26 6:48 ` Alex Riesen [this message]
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=20080726064831.GA3698@blimp.local \
--to=raa.lkml@gmail.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
/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).