archive mirror
 help / color / mirror / Atom feed
From: Junio C Hamano <>
To: "brian m. carlson" <>
Cc: "Ævar Arnfjörð Bjarmason" <>,,
	"Carlo Marcelo Arenas Belón" <>
Subject: Re: [PATCH 2/2] Remove support for v1 of the PCRE library
Date: Sat, 23 Jan 2021 21:14:43 -0800	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <> (brian m. carlson's message of "Sun, 24 Jan 2021 03:21:53 +0000")

"brian m. carlson" <> writes:

> On 2021-01-24 at 01:58:33, Ævar Arnfjörð Bjarmason wrote:
>> Remove support for using version 1 of the PCRE library. Its use has
>> been discouraged by upstream for a long time, and it's in a
>> bugfix-only state.
>> Anyone who was relying on v1 in particular got a nudge to move to v2
>> in e6c531b808 (Makefile: make USE_LIBPCRE=YesPlease mean v2, not v1,
>> 2018-03-11), which was first released as part of v2.18.0.
>> With this the LIBPCRE2 test prerequisites is redundant to PCRE. But
>> I'm keeping it for self-documentation purposes, and to avoid conflict
>> with other in-flight PCRE patches.
> I think it's fine to drop support for the original PCRE.  All supported
> versions of CentOS, Debian, Ubuntu, FreeBSD, and NetBSD have PCRE2 by
> now, and I'm quite fine with giving folks using systems without security
> updates a bit of a wake-up call.  I have no reason to believe that any
> other major operating system won't have version 2, either.
> So, essentially, I think this is a good idea.

Yeah, I too like seeing the world making progress ;-).

  reply	other threads:[~2021-01-24  5:15 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-24  1:58 [PATCH 1/2] config.mak.uname: remove redundant NO_LIBPCRE1_JIT flag Ævar Arnfjörð Bjarmason
2021-01-24  1:58 ` [PATCH 2/2] Remove support for v1 of the PCRE library Ævar Arnfjörð Bjarmason
2021-01-24  3:21   ` brian m. carlson
2021-01-24  5:14     ` Junio C Hamano [this message]
2021-01-28 15:44 ` [PATCH 1/2] config.mak.uname: remove redundant NO_LIBPCRE1_JIT flag Johannes Schindelin

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \ \

* 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 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 NNTP newsgroup(s).