From: William Morgan <wmorgan-sup@masanjin.net>
To: Sup-talk mailing list <sup-talk@rubyforge.org>
Subject: Re: [sup-talk] Recovering a busted ferret db?
Date: Mon, 02 Nov 2009 04:35:21 -0800 [thread overview]
Message-ID: <1257165314-sup-679@masanjin.net> (raw)
In-Reply-To: <1257162594-sup-7077@masanjin.net>
Reformatted excerpts from William Morgan's message of 2009-11-02:
> I'm going to apply the patch, but with a bigger limit.
Actually, strike that. The patch would mean we effectively limit the
number of recipients in a to, cc, or bcc field, which seems crazy. It
would be better to reimplement the regexp as a little state machine, as
irritating as that might be.
Steven, can you privately send me the header that's causing this? You
can obscure it somewhat if you want, just leave the quotes and commas
alone.
--
William <wmorgan-sup@masanjin.net>
_______________________________________________
sup-talk mailing list
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk
prev parent reply other threads:[~2009-11-02 12:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-30 17:17 Steven Walter
2009-10-30 21:48 ` William Morgan
2009-10-30 22:14 ` Steven Walter
2009-11-01 14:53 ` William Morgan
[not found] ` <e06498070911011203s66ece542mac80378442073369@mail.gmail.com>
2009-11-02 11:53 ` William Morgan
2009-11-02 12:35 ` William Morgan [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=1257165314-sup-679@masanjin.net \
--to=wmorgan-sup@masanjin.net \
--cc=sup-talk@rubyforge.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