From: Stainless Steel Rat <ratinox@ccs.neu.edu>
Subject: Re: reading .overview files takes too long!
Date: Sun, 20 Oct 2002 20:10:43 +0000 (UTC) [thread overview]
Message-ID: <420.807165983383$1042178861@news.gmane.org> (raw)
X-Geek-3: GAT d-(++)@ s: a-
C+(++) US++++$ P++>+++ L>+++ E+++ W++ N+++ K++++ w---$ O?>++ M-$ V-
PS+ PE Y+(++) PGP++ !t 5++ X? R(+) tv b+++ DI+ D++ G+ e+>++(*) h! r y+
References: <199510260915.CAA15950@mir.cs.washington.edu>
<199510261440.KAA27436@catfish.lcs.mit.edu>
<199510261545.IAA04484@meitner.cs.washington.edu>
<w8szqein1t3.fsf@surt.ifi.uio.no>
<199510302142.WAA06042@ssv4.dina.kvl.dk>
<w8sivl3adkt.fsf_-_@surt.ifi.uio.no>
Date: 02 Nov 1995 10:04:12 -0500
In-Reply-To: larsi@ifi.uio.no's message of 02 Nov 1995 04:40:50 +0100
Message-ID: <sr3fc783df.fsf@delphi.ccs.neu.edu>
Lines: 29
-----BEGIN PGP SIGNED MESSAGE-----
>>>>> "LMI" == Lars Magne Ingebrigtsen <larsi@ifi.uio.no> writes:
LMI> But the number of threads in a typical group usually is seldom over
LMI> 100, which means that the time saved might be lost in the extra
LMI> overhead... but probably not.
I dunnow about that. I read a bunch of newsgroups that average 150-200
or more messages per day, not to mention my list owner mail groups that
can receive a huge pile of bounce messages on one of the high-traffic
lists I maintain (100 messages per day times three bad addresses equals
a boatload of bounces).
-----BEGIN PGP SIGNATURE-----
Version: 2.6.2
Comment: Processed by Mailcrypt 3.4, an Emacs/PGP interface
iQCVAwUBMJjd5J6VRH7BJMxHAQHo3QP9HW16zcqQaJ5yY+Aw93HqqScRkn+i5cGS
giIAPEANaMME8xl1hCCnQQImZhRWQgw7UVt/FyADXwUw9K1yTglUcpOkaY3vk56P
qDtXRgQHntV71E1oYX7TECiBIPGqfxjqFVfDSV4nyM8a3RRkdrXZUSHxf0QxSs7k
EosOvG6BAoA=
=XHh1
-----END PGP SIGNATURE-----
--
Rat <ratinox@ccs.neu.edu> \ Warning: pregnant women, the elderly, and
PGP Public Key: Ask for one today! \ children under 10 should avoid prolonged
http://www.ccs.neu.edu/home/ratinox/ \ exposure to Happy Fun Ball.
next reply other threads:[~2002-10-20 20:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-20 20:10 Stainless Steel Rat [this message]
[not found] <199510260915.CAA15950@mir.cs.washington.edu>
[not found] ` <199510261440.KAA27436@catfish.lcs.mit.edu>
[not found] ` <199510261545.IAA04484@meitner.cs.washington.edu>
[not found] ` <w8szqein1t3.fsf@surt.ifi.uio.no>
[not found] ` <199510302142.WAA06042@ssv4.dina.kvl.dk>
1995-11-02 3:40 ` Lars Magne Ingebrigtsen
[not found] ` <sr3fc783df.fsf@delphi.ccs.neu.edu>
1995-11-06 13:32 ` 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='420.807165983383$1042178861@news.gmane.org' \
--to=ratinox@ccs.neu.edu \
/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).