From: Kai.Grossjohann@CS.Uni-Dortmund.DE
Subject: Re: crossposted mail articles not expired?
Date: 19 Dec 1998 02:16:49 +0100 [thread overview]
Message-ID: <86vhj9szge.fsf@slowfox.cs.uni-dortmund.de> (raw)
In-Reply-To: soma@cs.unm.edu's message of "18 Dec 1998 09:52:31 -0700"
I think there was some discussion on handling expiry a year or so
ago. The consensus seemed to be that something should be done about
it, and there should be ways of saying:
- delete this article from this group
- delete this article from all groups
Here, `delete' means after the expiry wait time, of course.
For the moment, you can do two things:
(1) Use total-expire and gnus-use-cross-reference.
This means that articles will be removed from all groups when
marked as read. Ticking an article means it will stay in that
group, I think.
(2) Else.
This means that each copy is treated separately.
kai
--
This gubblick contains many nonsklarkish English flutzpahs,
but the overall pluggandisp can be glorked from context. -- David Moser
prev parent reply other threads:[~1998-12-19 1:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-12-18 16:52 Anil B. Somayaji
1998-12-18 17:48 ` Graham Murray
1998-12-18 18:08 ` Anil B. Somayaji
1998-12-20 6:49 ` Yair Friedman
1998-12-18 21:29 ` Matt Armstrong
1998-12-19 1:16 ` Kai.Grossjohann [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=86vhj9szge.fsf@slowfox.cs.uni-dortmund.de \
--to=kai.grossjohann@cs.uni-dortmund.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).