From: Johannes Sixt <j.sixt@viscovery.net>
To: Scott Parish <sRp@srparish.net>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] allow git to use the PATH for finding subcommands and help docs
Date: Fri, 19 Oct 2007 15:21:12 +0200 [thread overview]
Message-ID: <4718AF48.9020607@viscovery.net> (raw)
In-Reply-To: <20071019130402.GD1463@srparish.net>
Scott Parish schrieb:
> I have a situation where software for a distribution is installed
> into a fake "prefix" and then moved to one of several potential
> places to be used by users. Given that the final location isn't
> static, i can't depend on builtin_exec_path. I'd really like users
> to be able to get started with git as easily as possible. With the
> current setup, they would have to create and maintain either an
> GIT_EXEC_PATH or an alias for including --exec-path, as well as a
> MANPATH and PERL5LIB. This seem like an unnessisary burden.
Interesting. How does this compare to this 2-patch-series:
http://repo.or.cz/w/git/mingw.git?a=commitdiff;h=e479ea2f911b8c70a269ba59372a4fef90f8907c
http://repo.or.cz/w/git/mingw.git?a=commitdiff;h=00a4ff4f3f8ec7e6b3ac15456f00b22b03f438ae
which I had come up with to accomplish something very similar
(on Windows). Your approach looks superior, but I hadn't gone
into depths, yet.
-- Hannes
next prev parent reply other threads:[~2007-10-19 13:48 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 [this message]
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
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=4718AF48.9020607@viscovery.net \
--to=j.sixt@viscovery.net \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.