From: Dan Jacques <dnj@google.com>
To: avarab@gmail.com
Cc: dnj@google.com, git@vger.kernel.org, gitster@pobox.com,
johannes.schindelin@gmx.de
Subject: Re: [PATCH v5 2/3] Makefile: add Perl runtime prefix support
Date: Mon, 8 Jan 2018 17:18:13 -0500 [thread overview]
Message-ID: <20180108221813.66805-1-dnj@google.com> (raw)
In-Reply-To: <877essatef.fsf@evledraar.gmail.com>
On Mon, 08 Jan 2018, Ævar Arnfjörð Bjarmason wrote:
> > I'll add a "NO_RUNTIME_PREFIX_PERL" flag as per avarab@'s suggestion as a
> > potential mitigation if a problem does end up arising in Windows builds,
> > with a note that NO_RUNTIME_PREFIX_PERL can be deleted if everything seems
> > to be working. What do you think?
>
> To be clear, I meant that if it's determined by you/others that an
> opt-out on Windows is needed I think it makes sense to make it a NO_*
> flag, but if there's a solution where we can just turn it on for
> everything then ideally we'd just have RUNTIME_PREFIX=YesPlease.
Oh that's fair. Okay, we'll go all in and just have RUNTIME_PREFIX.
next prev parent reply other threads:[~2018-01-08 22:18 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-08 3:02 [PATCH v5 0/3] RUNTIME_PREFIX relocatable Git Dan Jacques
2018-01-08 3:02 ` [PATCH v5 1/3] Makefile: generate Perl header from template file Dan Jacques
2018-01-08 3:02 ` [PATCH v5 2/3] Makefile: add Perl runtime prefix support Dan Jacques
2018-01-08 9:41 ` Ævar Arnfjörð Bjarmason
2018-01-08 19:18 ` Dan Jacques
2018-01-08 20:00 ` Ævar Arnfjörð Bjarmason
2018-01-08 20:27 ` Johannes Schindelin
2018-01-08 21:54 ` Junio C Hamano
2018-01-08 22:05 ` Dan Jacques
2018-01-08 22:16 ` Ævar Arnfjörð Bjarmason
2018-01-08 22:18 ` Dan Jacques [this message]
2018-01-08 20:24 ` Johannes Schindelin
2018-01-08 3:02 ` [PATCH v5 3/3] exec_cmd: RUNTIME_PREFIX on some POSIX systems Dan Jacques
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20180108221813.66805-1-dnj@google.com \
--to=dnj@google.com \
--cc=avarab@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=johannes.schindelin@gmx.de \
/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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).