From: gsstark@MIT.EDU (Greg Stark)
Subject: caching articles in a digest group?
Date: 10 Mar 1996 17:10:23 -0500 [thread overview]
Message-ID: <ycq7mwsfvlc.fsf@fierce-bad-rabbit.MIT.EDU> (raw)
September Gnus v0.51; nntp 4.0; nnml 1.0; nndoc 1.0; nnfolder 1.0
GNU Emacs 19.30.1 (mips-dec-ultrix4.2, X toolkit) of Mon Jan 8 1996 on yaz-pistachio
So I just hit * on an article in a digest group, ding happily cached it in a
directory called nndoc:comp.risks-1180 which, near as i can tell it never uses
later. I'm not sure what should happen here, but it probably shouldn't let me
gobble up disk quota for no purpose. I suspect the Right Thing probably
involves the thing we've been discussing that would allow following threads
through multiple digests. I think this demonstrates a new requirement of any
solution to that problem: it should be possible to save old articles from old
digests and have them be threaded properly with the new articles.
greg
next reply other threads:[~1996-03-10 22:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
1996-03-10 22:10 Greg Stark [this message]
1996-03-11 4:56 ` Lars Magne Ingebrigtsen
1996-03-11 8:07 ` Greg Stark
1996-03-11 19:54 ` 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=ycq7mwsfvlc.fsf@fierce-bad-rabbit.MIT.EDU \
--to=gsstark@mit.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).