From: Junio C Hamano <gitster@pobox.com>
To: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>
Cc: "Johannes Schindelin" <Johannes.Schindelin@gmx.de>,
"Git Mailing List" <git@vger.kernel.org>,
"Nguyễn Thái Ngọc Duy" <pclouds@gmail.com>
Subject: Re: PCRE v2 compile error, was Re: What's cooking in git.git (May 2017, #01; Mon, 1)
Date: Mon, 08 May 2017 16:10:41 +0900 [thread overview]
Message-ID: <xmqqpofj7rim.fsf@gitster.mtv.corp.google.com> (raw)
In-Reply-To: <CACBZZX75nvfQft-gjUG+YP0Y-e-=Knm3bMeDWHSUF=Juz9Ua5Q@mail.gmail.com> ("Ævar Arnfjörð Bjarmason"'s message of "Mon, 8 May 2017 08:30:56 +0200")
Ævar Arnfjörð Bjarmason <avarab@gmail.com> writes:
> This won't be in my next PCRE submission, but I have a path locally to
> simply import PCRE into git.git as compat/pcre2, so it can be compiled
> with NO_PCRE=Y similar to how NO_REGEX=Y works.
>
> This will hopefully address your concerns partially, i.e. when you do
> want to try it out it'll be easier.
Eek, please don't.
Until pcre2 becomes _so_ stable that all reasonable distros give
choice to the end-users to install it easily in a packaged form,
such a "not a fork, but a copy" will be a moving target that I'd
rather not to have in compat/. IOW, our compat/$pkg should be a
last resort to help those on distros that are so hard to convince to
carry the version/variant of $pkg we would like to use.
next prev parent reply other threads:[~2017-05-08 7:10 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-01 5:35 What's cooking in git.git (May 2017, #01; Mon, 1) Junio C Hamano
2017-05-01 14:25 ` Ævar Arnfjörð Bjarmason
2017-05-01 16:21 ` Brandon Williams
2017-05-01 17:44 ` Ævar Arnfjörð Bjarmason
2017-05-01 19:29 ` Jeff King
2017-05-01 23:21 ` Junio C Hamano
2017-05-02 8:23 ` Ævar Arnfjörð Bjarmason
2017-05-02 9:35 ` Junio C Hamano
2017-05-02 12:31 ` Ævar Arnfjörð Bjarmason
2017-05-02 11:11 ` Johannes Schindelin
2017-05-02 12:09 ` PCRE v2 compile error, was " Johannes Schindelin
2017-05-02 12:27 ` Ævar Arnfjörð Bjarmason
2017-05-02 16:05 ` Johannes Schindelin
2017-05-02 18:52 ` Ævar Arnfjörð Bjarmason
2017-05-02 20:51 ` Kevin Daudt
2017-05-02 21:16 ` Ævar Arnfjörð Bjarmason
2017-05-03 9:45 ` Johannes Schindelin
2017-05-03 11:15 ` Duy Nguyen
2017-05-03 15:10 ` Ævar Arnfjörð Bjarmason
2017-05-04 9:11 ` Johannes Schindelin
2017-05-04 10:24 ` Ævar Arnfjörð Bjarmason
2017-05-04 11:32 ` Johannes Schindelin
2017-05-04 11:53 ` Ævar Arnfjörð Bjarmason
2017-05-08 6:30 ` Ævar Arnfjörð Bjarmason
2017-05-08 7:10 ` Junio C Hamano [this message]
2017-05-08 23:32 ` brian m. carlson
2017-05-09 0:00 ` Ævar Arnfjörð Bjarmason
2017-05-09 0:37 ` brian m. carlson
2017-05-09 10:40 ` Johannes Schindelin
2017-05-09 11:29 ` Ævar Arnfjörð Bjarmason
2017-05-09 11:12 ` Ævar Arnfjörð Bjarmason
2017-05-09 14:22 ` demerphq
2017-05-09 14:46 ` Ævar Arnfjörð Bjarmason
2017-05-02 17:43 ` Brandon Williams
2017-05-02 17:49 ` Ævar Arnfjörð Bjarmason
2017-05-05 1:12 ` Ramsay Jones
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=xmqqpofj7rim.fsf@gitster.mtv.corp.google.com \
--to=gitster@pobox.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=avarab@gmail.com \
--cc=git@vger.kernel.org \
--cc=pclouds@gmail.com \
/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).