From: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>
To: git@vger.kernel.org
Cc: "Junio C Hamano" <gitster@pobox.com>,
"Nguyễn Thái Ngọc Duy" <pclouds@gmail.com>,
"Jeff King" <peff@peff.net>,
"Ævar Arnfjörð Bjarmason" <avarab@gmail.com>
Subject: [PATCH 0/2] wildmatch precompilation interface
Date: Sun, 25 Feb 2018 20:35:35 +0000 [thread overview]
Message-ID: <20180225203537.28318-1-avarab@gmail.com> (raw)
My recently landed wildmatch test series was in preperation for some
more major wildmatch changes.
Here's another series that prepares for bigger changes in wildmatch,
it adds an interface to pre-compile the patterns. Right now there's no
point in doing this, and it's harmless since none of the codepaths are
that performance sensitive, but down the line this'll save us time as
we'll be able to skip re-parsing the pattern each time with a better
wildmatch backend.
Ævar Arnfjörð Bjarmason (2):
wildmatch: add interface for precompiling wildmatch() patterns
wildmatch: use the new precompiling wildmatch()
builtin/name-rev.c | 7 ++++++-
builtin/replace.c | 7 ++++---
config.c | 8 ++++++--
refs.c | 7 ++++---
wildmatch.c | 25 +++++++++++++++++++++++++
wildmatch.h | 11 +++++++++++
6 files changed, 56 insertions(+), 9 deletions(-)
--
2.15.1.424.g9478a66081
next reply other threads:[~2018-02-25 20:35 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-25 20:35 Ævar Arnfjörð Bjarmason [this message]
2018-02-25 20:35 ` [PATCH 1/2] wildmatch: add interface for precompiling wildmatch() patterns Ævar Arnfjörð Bjarmason
2018-02-26 10:53 ` Duy Nguyen
2018-02-26 12:19 ` Ævar Arnfjörð Bjarmason
2018-02-25 20:35 ` [PATCH 2/2] wildmatch: use the new precompiling wildmatch() Ævar Arnfjörð Bjarmason
2018-02-26 11:00 ` Duy Nguyen
2018-02-26 12:17 ` Ævar Arnfjörð Bjarmason
2018-02-26 11:01 ` [PATCH 0/2] wildmatch precompilation interface Duy Nguyen
2018-02-26 12:34 ` Æ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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20180225203537.28318-1-avarab@gmail.com \
--to=avarab@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=pclouds@gmail.com \
--cc=peff@peff.net \
/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.
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).