From: jvinson@cheux.ecs.umass.edu (Jack Vinson)
Subject: cached articles
Date: 14 Dec 1995 09:28:35 -0500 [thread overview]
Message-ID: <wospinzpm4.fsf@cheux.ecs.umass.edu> (raw)
Can someone clear up what we've done to article caching?
In the past if we had article caching turned on and marked an article with
! or ? (tick or dormant) that article would be cached so that it didn't
disappear when the group went through its expiry process.
Now it sounds like we have broken this behavior by creating a separate mark
(*) which will automagically cache an article. Is this the case? If so,
this means that I have to remember to cache articles that I might want to
keep around instead of ticking them, correct?
--
Jonathan "Jack" Vinson jvinson@cheux.ecs.umass.edu
Sunderland, MA <http://www.cis.upenn.edu/~vinson/home.html>
"Churchill was a shopping bag" - Fatima Mansions
next reply other threads:[~1995-12-14 14:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
1995-12-14 14:28 Jack Vinson [this message]
1995-12-14 16:20 ` Dave Disser
1995-12-14 19:38 ` Lars Magne Ingebrigtsen
1995-12-15 19:07 ` Lars Magne Ingebrigtsen
1995-12-14 19:38 ` Lars Magne Ingebrigtsen
1995-12-15 19:07 ` 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=wospinzpm4.fsf@cheux.ecs.umass.edu \
--to=jvinson@cheux.ecs.umass.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).