From: Stefan Richter <stefanr@s5r6.in-berlin.de>
To: Cal Peake <cp@absolutedigital.net>
Cc: Joe Perches <joe@perches.com>,
"Kok, Auke" <auke-jan.h.kok@intel.com>,
Alan Cox <alan@lxorguk.ukuu.org.uk>,
torvalds@linux-foundation.org, linux-kernel@vger.kernel.org,
akpm@linux-foundation.org, Eng.Linux@digi.com
Subject: Re: [PATCH] [154/2many] MAINTAINERS - DIGI INTL. EPCA DRIVER
Date: Tue, 14 Aug 2007 22:38:02 +0200 [thread overview]
Message-ID: <46C212AA.1040409@s5r6.in-berlin.de> (raw)
In-Reply-To: <Pine.LNX.4.64.0708140040280.11945@lancer.cnet.absolutedigital.net>
Cal Peake wrote:
> On Mon, 13 Aug 2007, Joe Perches wrote:
>
>> On Tue, 2007-08-14 at 00:29 -0400, Cal Peake wrote:
>>> Prolly /[^a-z0-9]/i would the safest bet. Also don't forget to escape
>>> double quotes (e.g. "Jonathan \"Jon\" Doe" <jon@example.net>).
>> A-Z and [[:space:]] are OK too.
>
> The 'i' at the end of the regex means case-insensitive ;) but yes, I
> forgot whitespace. So something like:
>
> if ($name =~ /[^a-z0-9[:space:]]/i) {
> quote_name;
> }
>
>> I skimmed the spec, but nothing jumped out at me.
>
> My recommendation was mostly based on what pine does. It seems to be a
> pretty sane MUA...
Better: Dig out the respective RFCs or/and use a library (perl module
or whatever) for the recoding into mail header formats.
--
Stefan Richter
-=====-=-=== =--- -===-
http://arcgraph.de/sr/
prev parent reply other threads:[~2007-08-14 20:38 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-13 6:26 joe
2007-08-13 10:53 ` Alan Cox
2007-08-13 14:45 ` Stefan Richter
2007-08-13 15:35 ` Alan Cox
2007-08-13 16:15 ` Kok, Auke
2007-08-13 16:35 ` Joe Perches
2007-08-14 4:13 ` Joe Perches
2007-08-14 4:29 ` Cal Peake
2007-08-14 4:39 ` Joe Perches
2007-08-14 4:52 ` Cal Peake
2007-08-14 20:38 ` Stefan Richter [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=46C212AA.1040409@s5r6.in-berlin.de \
--to=stefanr@s5r6.in-berlin.de \
--cc=Eng.Linux@digi.com \
--cc=akpm@linux-foundation.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=auke-jan.h.kok@intel.com \
--cc=cp@absolutedigital.net \
--cc=joe@perches.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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
all inboxes | Powered by JetHome®