From: Jack Twilley <jmt+usenet@twilley.org>
Subject: Re: Why does Gnus load 2.5M to read one message?
Date: Sat, 09 Mar 2002 14:05:04 -0800 [thread overview]
Message-ID: <86sn79z9bj.fsf@duchess.twilley.org> (raw)
In-Reply-To: <a6dshl$qtk$1@quimby.gnus.org>
There may be an error in the status line kilobyte counter.
Either that or to read one article in this group took 13700+
kilobytes.
Jack.
--
Jack Twilley
jmt at twilley dot org
http colon slash slash www dot twilley dot org slash tilde jmt slash
next prev parent reply other threads:[~2002-03-09 22:05 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-08 23:00 Jack Twilley
2002-03-09 16:37 ` Kai Großjohann
2002-03-09 16:37 ` Kai Großjohann
2002-03-09 19:39 ` Jack Twilley
2002-03-09 19:47 ` ShengHuo ZHU
2002-03-09 20:45 ` Jack Twilley
2002-03-11 15:53 ` Kai Großjohann
2002-03-11 17:12 ` Per Abrahamsen
[not found] ` <a6dshl$qtk$1@quimby.gnus.org>
2002-03-09 22:05 ` Jack Twilley [this message]
2002-03-09 19:47 ` ShengHuo ZHU
2002-03-09 19:39 ` Jack Twilley
-- strict thread matches above, loose matches on Subject: below --
2002-03-08 23:00 Jack Twilley
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=86sn79z9bj.fsf@duchess.twilley.org \
--to=jmt+usenet@twilley.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).