From: Reiner Steib <4uce.02.r.steib@gmx.net>
Subject: Re: WARNING: The attached message make Gnus eat all resources
Date: Tue, 23 Jul 2002 19:57:56 +0200 [thread overview]
Message-ID: <v9u1mql42j.fsf@marauder.physik.uni-ulm.de> (raw)
In-Reply-To: <m3ptxe8pjr.fsf@fermat.mts.jhu.edu>
On Tue, Jul 23 2002, Nevin Kapur wrote:
> The attached message will make Gnus eat all resources for a *long*
> time -- I C-g'd after about a minute. Debug on quit suggests
> something to do with flow-fill and filladapt in turn.
I can display this message (directly in gmane.comp.security.bugtraq)
without any problems. I use GNU Emacs 21.1.1, Oort Gnus v0.07. (I have
no special setting related to filling.)
Bye, Reiner.
--
,,,
(o o)
---ooO-(_)-Ooo--- PGP key available via WWW http://rsteib.home.pages.de/
next prev parent reply other threads:[~2002-07-23 17:57 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-23 14:58 Nevin Kapur
2002-07-23 17:57 ` Reiner Steib [this message]
2002-07-23 18:10 ` Josh Huber
2002-07-23 20:11 ` Harry Putnam
2002-07-24 7:40 ` Niklas Morberg
2002-07-26 12:53 ` Simon Josefsson
2002-07-26 15:40 ` Nevin Kapur
2002-07-26 16:39 ` Simon Josefsson
2002-07-28 14:47 ` Nevin Kapur
2002-12-30 17:19 ` Lars Magne Ingebrigtsen
2002-12-30 17:17 ` Lars Magne Ingebrigtsen
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=v9u1mql42j.fsf@marauder.physik.uni-ulm.de \
--to=4uce.02.r.steib@gmx.net \
--cc=reiner.steib@gmx.de \
/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).