From: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>
To: git@vger.kernel.org
Cc: "Junio C Hamano" <gitster@pobox.com>, "Jeff King" <peff@peff.net>,
"Jeffrey Walton" <noloader@gmail.com>,
"Michał Kiedrowicz" <michal.kiedrowicz@gmail.com>,
"J Smith" <dark.panda@gmail.com>,
"Victor Leschuk" <vleschuk@gmail.com>,
"Nguyễn Thái Ngọc Duy" <pclouds@gmail.com>,
"Fredrik Kuivinen" <frekui@gmail.com>,
"Brandon Williams" <bmwill@google.com>,
"Stefan Beller" <sbeller@google.com>,
"Johannes Schindelin" <johannes.schindelin@gmx.de>,
"Ævar Arnfjörð Bjarmason" <avarab@gmail.com>
Subject: [PATCH v3 0/7] PCRE v2, PCRE v1 JIT, log -P & fixes
Date: Thu, 25 May 2017 20:05:21 +0000 [thread overview]
Message-ID: <20170525200528.22037-1-avarab@gmail.com> (raw)
See <20170523192453.14172-1-avarab@gmail.com> for v2
(https://public-inbox.org/git/20170523192453.14172-1-avarab@gmail.com/).
This on top of "[PATCH v4 00/31] Easy to review grep & pre-PCRE
changes".
This hopefully addresses all the comments I had on v2. Comments below:
Ævar Arnfjörð Bjarmason (7):
grep: don't redundantly compile throwaway patterns under threading
grep: skip pthreads overhead when using one thread
log: add -P as a synonym for --perl-regexp
No changes.
grep: add support for the PCRE v1 JIT API
* Simplify logic around canjit variable.
* s/BUG: // for things that aren't internal bugs (but keep it for one
that's an actual bug if it happens...)
* Simplify syntax around `#ifdef PCRE_CONFIG_JIT` blocks.
grep: un-break building with PCRE < 8.32
* Reword commit message for less confusion.
* Macro name: s/GIT_PCRE1_CAN_DO_MODERN_JIT/GIT_PCRE1_USE_JIT/g
grep: un-break building with PCRE < 8.20
No changes.
grep: add support for PCRE v2
* Makefile: Clarify comment about what LIBPCREDIR=* does now.
* Makefile: One use of USE_LIBPCRE is now USE_LIBPCRE1. It's
logically the same, but less confusing now.
* grep.c: Fix up comment syntax
* grep.c: Same canjit & s/BUG: // bug fixes as noted for PCRE v1.
Documentation/rev-list-options.txt | 1 +
Makefile | 36 +++++--
builtin/grep.c | 16 +++-
configure.ac | 77 ++++++++++++---
grep.c | 187 ++++++++++++++++++++++++++++++++++++-
grep.h | 31 ++++++
revision.c | 2 +-
t/t4202-log.sh | 12 +++
t/test-lib.sh | 2 +-
9 files changed, 335 insertions(+), 29 deletions(-)
--
2.13.0.303.g4ebf302169
next reply other threads:[~2017-05-25 20:05 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-25 20:05 Ævar Arnfjörð Bjarmason [this message]
2017-05-25 20:05 ` [PATCH v3 1/7] grep: don't redundantly compile throwaway patterns under threading Ævar Arnfjörð Bjarmason
2017-05-25 20:05 ` [PATCH v3 2/7] grep: skip pthreads overhead when using one thread Ævar Arnfjörð Bjarmason
2017-05-25 20:05 ` [PATCH v3 3/7] log: add -P as a synonym for --perl-regexp Ævar Arnfjörð Bjarmason
2017-05-25 20:05 ` [PATCH v3 4/7] grep: add support for the PCRE v1 JIT API Ævar Arnfjörð Bjarmason
2017-05-25 20:05 ` [PATCH v3 5/7] grep: un-break building with PCRE < 8.32 Ævar Arnfjörð Bjarmason
2017-05-25 20:05 ` [PATCH v3 6/7] grep: un-break building with PCRE < 8.20 Ævar Arnfjörð Bjarmason
2017-05-25 20:05 ` [PATCH v3 7/7] grep: add support for PCRE v2 Ævar Arnfjörð Bjarmason
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=20170525200528.22037-1-avarab@gmail.com \
--to=avarab@gmail.com \
--cc=bmwill@google.com \
--cc=dark.panda@gmail.com \
--cc=frekui@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=johannes.schindelin@gmx.de \
--cc=michal.kiedrowicz@gmail.com \
--cc=noloader@gmail.com \
--cc=pclouds@gmail.com \
--cc=peff@peff.net \
--cc=sbeller@google.com \
--cc=vleschuk@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).