From: Florian Weimer <fw@deneb.enyo.de>
Subject: Re: what's up with me reading comp.infosystems.www.authoring.cgi?
Date: 19 Apr 2001 12:34:12 +0200 [thread overview]
Message-ID: <87d7a9npp7.fsf@deneb.enyo.de> (raw)
In-Reply-To: <m1vgo1g4kd.fsf@halfdome.holdit.com> (merlyn@stonehenge.com's message of "18 Apr 2001 16:40:18 -0700")
merlyn@stonehenge.com (Randal L. Schwartz) writes:
> Hmm, maybe I should just blow away my entire cache.
The cache in general seems to be a cause of endless troubles. I once
had a cached article in an nnml group and renamed that group. :-/
prev parent reply other threads:[~2001-04-19 10:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-18 15:47 Randal L. Schwartz
2001-04-18 17:52 ` Karl Kleinpaste
2001-04-18 22:08 ` Randal L. Schwartz
2001-04-18 22:12 ` Karl Kleinpaste
2001-04-18 23:40 ` Randal L. Schwartz
2001-04-19 10:34 ` Florian Weimer [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=87d7a9npp7.fsf@deneb.enyo.de \
--to=fw@deneb.enyo.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).