From: Junio C Hamano <gitster@pobox.com>
To: git@vger.kernel.org
Subject: Re: [PATCH] Extend runtime prefix computation
Date: Tue, 16 Apr 2013 11:23:09 -0700 [thread overview]
Message-ID: <7vvc7ml4he.fsf@alter.siamese.dyndns.org> (raw)
In-Reply-To: <20130416145653.GG12782@science-computing.de> (nobody's message of "Tue, 16 Apr 2013 16:56:54 +0200")
nobody writes:
> Hello Junio,
> Hello list,
>
> On Wed, Mar 06, 2013 at 09:19:42AM +0100, Michael Weiser wrote:
>
>> > >> Support determining the binaries' installation path at runtime even if
>> > >> called without any path components (i.e. via search path).
>> > The default for any change is not to include it. Is there any
>> > reason why we want this change?
>> It makes a binary git installation fully relocatable. Seeing how git
>> already has basic support for it I thought other people might be
>> interested in this.
>
> I am still interested in getting this accepted into git. Where do I push
> to get it committed?
I do not have a strong objection to what it tries to achieve, but
I'd prefer to see no "#ifdef platform" code in a very generic part
of the system like exec_cmd.
next prev parent reply other threads:[~2013-04-16 18:23 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-27 16:30 [PATCH] Extend runtime prefix computation Michael Weiser
2012-11-30 10:20 ` Erik Faye-Lund
2012-11-30 10:45 ` Michael Weiser
2013-03-05 11:58 ` Michael Weiser
2013-03-05 16:13 ` Junio C Hamano
2013-03-06 8:19 ` Michael Weiser
2013-04-16 14:56 ` Michael Weiser
2013-04-16 18:23 ` Junio C Hamano [this message]
2013-04-16 15:18 ` Erik Faye-Lund
2013-04-17 6:06 ` Michael Weiser
2013-10-04 13:32 ` Michael Weiser
-- strict thread matches above, loose matches on Subject: below --
2016-04-15 14:30 Michael Weiser
2016-04-15 16:43 ` Junio C Hamano
2016-04-18 7:20 ` Johannes Schindelin
2016-04-20 17:52 ` Michael Weiser
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=7vvc7ml4he.fsf@alter.siamese.dyndns.org \
--to=gitster@pobox.com \
--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 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.