From: Jim Meyering <jim@meyering.net>
To: Paul Eggert <eggert@cs.ucla.edu>
Cc: fryasu@yahoo.co.jp, Gnulib bugs <bug-gnulib@gnu.org>,
40634@debbugs.gnu.org, Norihiro Tanaka <noritnk@kcn.ne.jp>,
GNU grep developers <grep-devel@gnu.org>
Subject: Re: bug#40634: Massive pattern list handling with -E format seems very slow since 2.28.
Date: Sat, 12 Sep 2020 08:41:51 +0200 [thread overview]
Message-ID: <CA+8g5KG=oYTb7fgVfCyWxGKxBEOhCK0LJPwb1DE3FQbd5ew0CQ@mail.gmail.com> (raw)
In-Reply-To: <0417af9a-50a5-3462-6b38-393d80395085@cs.ucla.edu>
On Sat, Sep 12, 2020 at 1:01 AM Paul Eggert <eggert@cs.ucla.edu> wrote:
> > And here is the adjusted patch:
>
> Hold on, that looks like a cleanup of the April 18 patch posted here:
>
> https://bugs.gnu.org/40634#26
>
> But there's a later patch dated April 19, which Norihiro Tanaka said should be
> more correct and simpler:
>
> https://bugs.gnu.org/40634#32
>
> I'll try to take a look at the later patch.
Oh! Glad you spotted that.
next prev parent reply other threads:[~2020-09-12 6:42 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <6503eb8e-e6fd-b4dd-aab7-76bb6955d87b@cs.ucla.edu>
[not found] ` <20200417093536.875E.27F6AC2D@kcn.ne.jp>
2020-04-17 1:24 ` bug#40634: Massive pattern list handling with -E format seems very slow since 2.28 Norihiro Tanaka
2020-04-17 15:22 ` Norihiro Tanaka
2020-04-18 22:41 ` Norihiro Tanaka
2020-04-19 2:10 ` Norihiro Tanaka
2020-09-11 12:47 ` Jim Meyering
2020-09-11 13:17 ` Jim Meyering
2020-09-11 23:01 ` Paul Eggert
2020-09-12 6:41 ` Jim Meyering [this message]
2020-09-14 2:03 ` Paul Eggert
2020-09-14 14:14 ` Jim Meyering
2020-09-21 19:22 ` Paul Eggert
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: https://lists.gnu.org/mailman/listinfo/bug-gnulib
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CA+8g5KG=oYTb7fgVfCyWxGKxBEOhCK0LJPwb1DE3FQbd5ew0CQ@mail.gmail.com' \
--to=jim@meyering.net \
--cc=40634@debbugs.gnu.org \
--cc=bug-gnulib@gnu.org \
--cc=eggert@cs.ucla.edu \
--cc=fryasu@yahoo.co.jp \
--cc=grep-devel@gnu.org \
--cc=noritnk@kcn.ne.jp \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).