From: Lars Magne Ingebrigtsen <larsi@ifi.uio.no>
Subject: Re: Soups and marks
Date: 17 Jun 1996 18:20:00 +0200 [thread overview]
Message-ID: <x6ohmicsi6.fsf@eyesore.no> (raw)
In-Reply-To: Kai Grossjohann's message of 17 Jun 1996 16:01:07 +0200
Kai Grossjohann <grossjoh@ls6.informatik.uni-dortmund.de> writes:
> Usually there two kinds of `read' messages: those that you want to
> delete and those that you want to keep. Without total-expire, the
> ones to delete are the `expirable' ones, the ones to keep the `read'
> ones. With total-expire, the ones to delete are the `read' ones
> whereas the ones to keep will be `ticked' or `dormant' (I suppose).
Yes, but SOUPing always assumes that you want to delete the messages.
(Which might be a faulty assumption.) If the group is auto-expirable,
the articles are marked as expirable; if it's a total-expirable group,
the articles are marked as read. Since the user takes a copy of the
articles when SOUPing, that seems like the most reasonable default
action to take.
--
"Yes. The journey through the human heart
would have to wait until some other time."
prev parent reply other threads:[~1996-06-17 16:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
1996-06-16 17:48 Kai Grossjohann
1996-06-17 2:22 ` Lars Magne Ingebrigtsen
1996-06-17 14:01 ` Kai Grossjohann
1996-06-17 16:20 ` Lars Magne Ingebrigtsen [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=x6ohmicsi6.fsf@eyesore.no \
--to=larsi@ifi.uio.no \
/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).