From: Justin Sheehy <justin@linus.mitre.org>
Subject: Re: [Q] same message in multiple groups & expiry
Date: 21 Jul 1997 09:51:10 -0400 [thread overview]
Message-ID: <glm90z0ms35.fsf@linus.mitre.org> (raw)
In-Reply-To: Kai Grossjohann's message of "18 Jul 1997 18:24:17 +0200"
Kai Grossjohann <grossjohann@charly.cs.uni-dortmund.de> writes:
> (1) Remove the group A copy but keep the group B copy. Mark the group
> B copy as read or dormant or something (optional).
>
> (2) Delete all copies of this message.
> - Mark as expirable; does this correspond to (1) or (2), or
> something else entirely?
Not exactly either.
Marking as expirable just marks it as expirable, it doesn't delete.
The expiry process will expire any articles that are marked expirable
and are older than expiry-wait. This is similar to (1) above.
Total-expire removes the need for the expirable mark.
With total expire, articles that are marked read and are older than
expiry-wait are deleted.
--
Justin Sheehy
In a cloud bones of steel.
prev parent reply other threads:[~1997-07-21 13:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
1997-07-18 16:24 Kai Grossjohann
1997-07-18 20:12 ` Colin Rafferty
1997-07-21 13:51 ` Justin Sheehy [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=glm90z0ms35.fsf@linus.mitre.org \
--to=justin@linus.mitre.org \
/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).