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>,
"Jonathan Nieder" <jrnieder@gmail.com>,
"Ævar Arnfjörð Bjarmason" <avarab@gmail.com>
Subject: [PATCH v4 0/2] perf: show that wildmatch() regressed for pathological cases in v2.0
Date: Thu, 11 May 2017 09:41:06 +0000 [thread overview]
Message-ID: <20170511094108.8756-1-avarab@gmail.com> (raw)
In-Reply-To: <20170511074354.11336-1-avarab@gmail.com>
Fixes a brainfart in v3. I thought I'd fixed that subshell cd issue,
but turns out I didn't, actually fix that.
Ævar Arnfjörð Bjarmason (2):
perf: add function to setup a fresh test repo
perf: add test showing exponential growth in path globbing
t/perf/README | 1 +
t/perf/p0100-globbing.sh | 43 +++++++++++++++++++++++++++++++++++++++++++
t/perf/perf-lib.sh | 19 +++++++++++++++----
3 files changed, 59 insertions(+), 4 deletions(-)
create mode 100755 t/perf/p0100-globbing.sh
--
2.11.0
next prev parent reply other threads:[~2017-05-11 9:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-11 7:43 [PATCH v3 0/2] perf: show that wildmatch() regressed for pathological cases in v2.0 Ævar Arnfjörð Bjarmason
2017-05-11 7:43 ` [PATCH v3 1/2] perf: add function to setup a fresh test repo Ævar Arnfjörð Bjarmason
2017-05-11 7:43 ` [PATCH v3 2/2] perf: add test showing exponential growth in path globbing Ævar Arnfjörð Bjarmason
2017-05-11 9:41 ` Ævar Arnfjörð Bjarmason [this message]
2017-05-11 19:17 ` [PATCH v4 0/2] perf: show that wildmatch() regressed for pathological cases in v2.0 Jonathan Nieder
2017-05-11 9:41 ` [PATCH v4 1/2] perf: add function to setup a fresh test repo Ævar Arnfjörð Bjarmason
2017-05-11 9:41 ` [PATCH v4 2/2] perf: add test showing exponential growth in path globbing Æ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=20170511094108.8756-1-avarab@gmail.com \
--to=avarab@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=jrnieder@gmail.com \
--cc=pclouds@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).