From: Tero Tilus <tero@tilus.net>
To: Sup developers <sup-devel@rubyforge.org>
Subject: [sup-devel] Message#text_to_chunks performance
Date: Thu, 28 Oct 2010 15:05:33 +0300 [thread overview]
Message-ID: <1288264300-sup-7747@tilus.net> (raw)
Hi,
I ran into an issue with bad behavior of Message#text_to_chunks on
long sequences of blank lines. Apparently I have and receive quite a
few mails with batshit crazy amounts of blank lines (the worst case
sofar being almost 200 kB worth of linefeeds ... don't ask) in them
and I want to be able to deal with them without needing to leave the
poll running overnight.
I have a naïve fix pushed to my sup fork at github (and gitorius too).
http://github.com/terotil/sup/tree/fix-text_to_chunks-performance
Is the patch-to-mailinglist still the preferred flow of contribution
as stated in Wiki? http://sup.rubyforge.org/wiki/wiki.pl?Contributing
Do you, Rich and William, take in (properly prepared) commits from
github/gitorius forks?
--
Tero Tilus ## 050 3635 235 ## http://tero.tilus.net/
_______________________________________________
Sup-devel mailing list
Sup-devel@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-devel
next reply other threads:[~2010-10-28 12:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-28 12:05 Tero Tilus [this message]
2010-11-04 16:05 ` Rich Lane
2010-12-21 21:45 ` Tero Tilus
2010-12-23 18:38 ` Rich Lane
2011-01-19 3:12 ` Rich Lane
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=1288264300-sup-7747@tilus.net \
--to=tero@tilus.net \
--cc=sup-devel@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