From: Junio C Hamano <gitster@pobox.com>
To: Johannes Sixt <j.sixt@viscovery.net>
Cc: Git Mailing List <git@vger.kernel.org>
Subject: Re: --exec-path not always honored
Date: Tue, 17 Mar 2009 22:41:34 -0700 [thread overview]
Message-ID: <7v7i2nmlpt.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: 49BF692B.9020002@viscovery.net
Johannes Sixt <j.sixt@viscovery.net> writes:
> git-gc is a builtin. Should git setenv("GIT_EXEC_PATH") before it runs
> other git commands?
I think we just never have bothered about such a use case, but you are
right. It probably is a good solution, although setenv makes me feel a
bit nervous for no rational reason.
next prev parent reply other threads:[~2009-03-18 5:43 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
2009-03-18 5:41 ` Junio C Hamano [this message]
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=7v7i2nmlpt.fsf@gitster.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=j.sixt@viscovery.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).