From: Kees de Bruin <kees_de_bruin@tasking.nl>
Subject: What is better for splitting: complex regexp or many rules
Date: 24 Oct 1996 08:49:49 +0200 [thread overview]
Message-ID: <ngramo97qq.fsf@tasking.nl> (raw)
I have a list of people I receive e-mail from and I would like to know what
is better: have a split entry for each person or create a complex regular
expression that matches all the e-mail addresses? The number of people
range from between 5 and 40 for a single split.
Kind regards,
--
Kees de Bruin Tasking Software BV
Software Engineer
---------------------------------------------------------------------------
telephone: +31 33 455 85 84 Tasking Software BV
fax: +31 33 455 10 05 Plotterweg 31
email: kees_de_bruin@tasking.com 3821 BB Amersfoort
WWW: http://www.tasking.com The Netherlands
CompuServe: GO TASKING
---------------------------------------------------------------------------
----- Quality Development Tools Worldwide -----
-----------------------------------
next reply other threads:[~1996-10-24 6:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
1996-10-24 6:49 Kees de Bruin [this message]
1996-10-25 7:56 ` Lars Magne Ingebrigtsen
1996-10-28 23:52 ` Danny Siu
1996-10-29 9:35 ` Per Abrahamsen
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=ngramo97qq.fsf@tasking.nl \
--to=kees_de_bruin@tasking.nl \
/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).