From: Marcelo Toledo <marcelo@marcelotoledo.org>
Subject: Re: small patch for nnmail (lowercase expand option)
Date: Fri, 09 Jul 2004 10:07:31 -0300 [thread overview]
Message-ID: <87hdsh9vn0.fsf@kali.intranet> (raw)
In-Reply-To: <b9yllhu54qh.fsf@jpl.org> (Katsumi Yamaoka's message of "Fri, 09 Jul 2004 10:49:58 +0900")
I've also ran into this problem, I fixed using regexp but I agree with
this patch.
Katsumi Yamaoka <yamaoka@jpl.org> writes:
> Is the option really needed? The value seems always one good at
> T because users cannot do case-sensitive splitting.
--
Marcelo Toledo
marcelo@marcelotoledo.org
http://www.marcelotoledo.org
Mobile: 55 71 9141-7181
next prev parent reply other threads:[~2004-07-09 13:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-08 23:06 dhedbor
2004-07-08 23:11 ` dhedbor
2004-07-09 1:49 ` Katsumi Yamaoka
2004-07-09 13:07 ` Marcelo Toledo [this message]
2004-07-09 15:49 ` Katsumi Yamaoka
2004-07-12 6:33 ` Katsumi Yamaoka
2004-07-12 17:08 ` dhedbor
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=87hdsh9vn0.fsf@kali.intranet \
--to=marcelo@marcelotoledo.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).