From: kai.grossjohann@uni-duisburg.de (Kai Großjohann)
Subject: Re: overview -> .db files?
Date: Thu, 07 Nov 2002 08:37:20 +0100 [thread overview]
Message-ID: <84lm45u8y7.fsf@crybaby.uni-duisburg.de> (raw)
In-Reply-To: <m3el9yiod8.fsf@multivac.cwru.edu>
prj@po.cwru.edu (Paul Jarc) writes:
> I think lots of things could invalidate the stored version, though.
> Changes in scoring, gnus-summary-line-format, article marks...
Yes. But most of the time, these things aren't changed, so reusing
the old data would be a win.
It seems the code that implements `/ N' already knows how to deal
with sorting and, probably, scoring. It's also quite fast. I wonder
if its ideas could be reused. I haven't looked at the code, so I
have no idea what's involved.
kai
--
~/.signature is: umop ap!sdn (Frank Nobis)
prev parent reply other threads:[~2002-11-07 7:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-31 16:07 Wes Hardaker
2002-10-31 18:21 ` Kai Großjohann
2002-10-31 21:03 ` Wes Hardaker
2002-11-01 17:42 ` Kai Großjohann
2002-11-06 17:44 ` Paul Jarc
2002-11-07 7:37 ` Kai Großjohann [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=84lm45u8y7.fsf@crybaby.uni-duisburg.de \
--to=kai.grossjohann@uni-duisburg.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).