From: Daniel Dehennin <daniel.dehennin@baby-gnu.org>
To: ding@gnus.org
Subject: Re: [PATCH] Optimize regexp build by Group Mail Splitting
Date: Sat, 01 Feb 2014 14:07:49 +0100 [thread overview]
Message-ID: <87ppn7yo9m.fsf@hati.baby-gnu.org> (raw)
In-Reply-To: <877g9fit3r.fsf@building.gnus.org> (Lars Ingebrigtsen's message of "Fri, 31 Jan 2014 16:17:44 -0800")
[-- Attachment #1: Type: text/plain, Size: 624 bytes --]
Lars Ingebrigtsen <larsi@gnus.org> writes:
[...]
> So it basically just uses `regexp-opt' instead of making the regexp
> itself "manually"? But the result is significantly slower, and the code
> doesn't seem to be shorter?
Right, but I abandoned this patch, I'll avoid the duplication between
“to-list” and “to-address” in another way in my rework of
“feature/group-mail-splitting-on-list-headers”.
Using “manual” alternative make the “nnmail-split-fancy” easier to read.
Regards.
--
Daniel Dehennin
Récupérer ma clef GPG:
gpg --keyserver pgp.mit.edu --recv-keys 0x7A6FE2DF
[-- Attachment #2: Type: application/pgp-signature, Size: 229 bytes --]
prev parent reply other threads:[~2014-02-01 13:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-28 3:53 Daniel Dehennin
2014-02-01 0:17 ` Lars Ingebrigtsen
2014-02-01 13:07 ` Daniel Dehennin [this message]
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=87ppn7yo9m.fsf@hati.baby-gnu.org \
--to=daniel.dehennin@baby-gnu.org \
--cc=ding@gnus.org \
/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).