From: Wes Hardaker <wjhardaker@ucdavis.edu>
Subject: Re: Can we have a message when agent expiry is finished?
Date: 13 Mar 1998 16:45:26 -0800 [thread overview]
Message-ID: <x74t12uml5.fsf@des.castles.com> (raw)
In-Reply-To: SL Baur's message of "13 Mar 1998 16:19:29 -0800"
>>>>> On 13 Mar 1998 16:19:29 -0800, SL Baur <steve@xemacs.org> said:
sb> I used to do this. The problem was that they disappear (by
sb> default) and don't reappear unless there is a (properly threaded)
sb> response. Has this changed?
I just tried it.
No.
And, even weirder, it doesn't show up when I enter a group I have set
up to show everything but non-expired articles... It must not
completely obey normal marking symbols?
--
"Ninjas aren't dangerous. They're more afraid of you than you are of them."
next prev parent reply other threads:[~1998-03-14 0:45 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-03-08 13:58 Mike McEwan
1998-03-13 21:13 ` Lars Magne Ingebrigtsen
1998-03-13 23:33 ` Wes Hardaker
1998-03-13 23:46 ` Hrvoje Niksic
1998-03-13 23:53 ` Wes Hardaker
1998-03-14 0:19 ` SL Baur
1998-03-14 0:45 ` Wes Hardaker [this message]
1998-03-15 1:06 ` Kai Grossjohann
1998-03-13 23:58 ` Lars Magne Ingebrigtsen
1998-03-14 0:08 ` SL Baur
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=x74t12uml5.fsf@des.castles.com \
--to=wjhardaker@ucdavis.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).