From: Johannes Sixt <j.sixt@viscovery.net>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: Git Mailing List <git@vger.kernel.org>
Subject: Re: --exec-path not always honored
Date: Tue, 17 Mar 2009 11:34:23 +0100 [thread overview]
Message-ID: <49BF7CAF.6060505@viscovery.net> (raw)
In-Reply-To: <alpine.DEB.1.00.0903171117480.6393@intel-tinevez-2-302>
Johannes Schindelin schrieb:
> On Tue, 17 Mar 2009, Johannes Sixt wrote:
>
>> I noticed this failure if I run git from the build directory:
>>
>> $ ./git --exec-path=. gc
>
> I am not sure if "." is what you think it is; I imagine it would be
> $GIT_DIR by the time the PATH variable is adjusted.
This would be *very* bogus, wouldn't it?
> Could you try again with
>
> $ ./git --exec-path="$(pwd)" gc
>
> ?
It fails in the same way:
$ ./git --exec-path=$(pwd) gc
usage: git pack-objects blah blah...
error: failed to run repack
-- Hannes
next prev parent reply other threads:[~2009-03-17 10:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-17 9:11 --exec-path not always honored Johannes Sixt
2009-03-17 10:19 ` Johannes Schindelin
2009-03-17 10:34 ` Johannes Sixt [this message]
2009-03-18 5:41 ` Junio C Hamano
2009-03-18 7:42 ` Johannes Sixt
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=49BF7CAF.6060505@viscovery.net \
--to=j.sixt@viscovery.net \
--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).