git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>
To: git@vger.kernel.org
Cc: "Junio C Hamano" <gitster@pobox.com>,
	"Ævar Arnfjörð Bjarmason" <avarab@gmail.com>
Subject: [PATCH 4/6] RelNotes: mention that PCRE v2 exposes the same syntax
Date: Thu, 20 Jul 2017 14:19:25 +0000	[thread overview]
Message-ID: <20170720141927.18274-5-avarab@gmail.com> (raw)
In-Reply-To: <20170720141927.18274-1-avarab@gmail.com>
In-Reply-To: <xmqq7ez6hk2y.fsf@gitster.mtv.corp.google.com>

For someone not familiar with PCRE or having read its own
documentation this isn't obvious, let's explicitly mention it so
package maintainers won't fear upgrading least they break things for
their users.

Signed-off-by: Ævar Arnfjörð Bjarmason <avarab@gmail.com>
---
 Documentation/RelNotes/2.14.0.txt | 3 +++
 1 file changed, 3 insertions(+)

diff --git a/Documentation/RelNotes/2.14.0.txt b/Documentation/RelNotes/2.14.0.txt
index 7ed93bca37..0e363f2af3 100644
--- a/Documentation/RelNotes/2.14.0.txt
+++ b/Documentation/RelNotes/2.14.0.txt
@@ -28,6 +28,9 @@ Backward compatibility notes and other notable changes.
    upstream PCRE maintainer has abandoned v1 maintenance for all but
    the most critical bug fixes, use of v2 is recommended.
 
+   Version v2 of the library is fully backwards compatible with the
+   Perl-compatible regular expression syntax exposed by git (sans a
+   few obscure bugfixes).
 
 Updates since v2.13
 -------------------
-- 
2.13.2.932.g7449e964c


  parent reply	other threads:[~2017-07-20 14:20 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-13 23:43 [ANNOUNCE] Git v2.14.0-rc0 Junio C Hamano
2017-07-14 23:17 ` Ævar Arnfjörð Bjarmason
2017-07-15  4:09   ` Christian Couder
2017-07-15 10:09     ` Ævar Arnfjörð Bjarmason
2017-07-17 20:41   ` Junio C Hamano
2017-07-18 20:03     ` Junio C Hamano
2017-07-20 14:19     ` [PATCH 0/6] 2.14 RelNotes improvements Ævar Arnfjörð Bjarmason
2017-07-20 20:35       ` Junio C Hamano
2017-07-21 11:03         ` Ævar Arnfjörð Bjarmason
2017-07-20 14:19     ` [PATCH 1/6] RelNotes: mention "log: add -P as a synonym for --perl-regexp" Ævar Arnfjörð Bjarmason
2017-07-20 14:19     ` [PATCH 2/6] RelNotes: mention "log: make --regexp-ignore-case work with --perl-regexp" Ævar Arnfjörð Bjarmason
2017-07-20 14:19     ` [PATCH 3/6] RelNotes: mention "sha1dc: optionally use sha1collisiondetection as a submodule" Ævar Arnfjörð Bjarmason
2017-07-20 14:19     ` Ævar Arnfjörð Bjarmason [this message]
2017-07-20 15:24       ` [PATCH 4/6] RelNotes: mention that PCRE v2 exposes the same syntax Junio C Hamano
2017-07-20 14:19     ` [PATCH 5/6] RelNotes: remove duplicate mention of PCRE v2 Ævar Arnfjörð Bjarmason
2017-07-20 15:26       ` Junio C Hamano
2017-07-20 14:19     ` [PATCH 6/6] RelNotes: add more notes about PCRE in 2.14 Ævar Arnfjörð Bjarmason
2017-07-20 19:11       ` Junio C Hamano

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=20170720141927.18274-5-avarab@gmail.com \
    --to=avarab@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.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).