git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>
Cc: git@vger.kernel.org, "Michał Kiedrowicz" <michal.kiedrowicz@gmail.com>
Subject: Re: [PATCH 0/3] Switch the default PCRE from v1 to v2 + configure fixes
Date: Wed, 14 Mar 2018 15:41:50 -0700	[thread overview]
Message-ID: <xmqqo9jqxosx.fsf@gitster-ct.c.googlers.com> (raw)
In-Reply-To: <20180311132609.32154-1-avarab@gmail.com> ("Ævar Arnfjörð Bjarmason"'s message of "Sun, 11 Mar 2018 13:26:06 +0000")

Ævar Arnfjörð Bjarmason  <avarab@gmail.com> writes:

> This small series makes USE_LIBPCRE=YesPlease mean
> USE_LIBPCRE2=YesPlease, instead of USE_LIBPCRE1=YesPlease is it does
> now. Along the way I fixed a couple of minor issues in the PCRE
> detection in the autoconf script.
>
> Ævar Arnfjörð Bjarmason (3):
>   configure: fix a regression in PCRE v1 detection
>   configure: detect redundant --with-libpcre & --with-libpcre1
>   Makefile: make USE_LIBPCRE=YesPlease mean v2, not v1
>
>  Makefile     | 26 +++++++++++++-------------
>  configure.ac | 26 +++++++++++++++-----------
>  2 files changed, 28 insertions(+), 24 deletions(-)

Makes sense.  Will queue.

      parent reply	other threads:[~2018-03-14 22:41 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-11 13:26 [PATCH 0/3] Switch the default PCRE from v1 to v2 + configure fixes Ævar Arnfjörð Bjarmason
2018-03-11 13:26 ` [PATCH 1/3] configure: fix a regression in PCRE v1 detection Ævar Arnfjörð Bjarmason
2018-03-11 13:26 ` [PATCH 2/3] configure: detect redundant --with-libpcre & --with-libpcre1 Ævar Arnfjörð Bjarmason
2018-03-11 13:26 ` [PATCH 3/3] Makefile: make USE_LIBPCRE=YesPlease mean v2, not v1 Ævar Arnfjörð Bjarmason
2018-03-14 22:41 ` Junio C Hamano [this message]

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=xmqqo9jqxosx.fsf@gitster-ct.c.googlers.com \
    --to=gitster@pobox.com \
    --cc=avarab@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=michal.kiedrowicz@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).