From: David S Goldberg <david.goldberg6@verizon.net>
Subject: Re: total and auto expiry
Date: Thu, 13 Mar 2003 13:54:13 -0500 [thread overview]
Message-ID: <u8zvfyn14iy.fsf@verizon.net> (raw)
In-Reply-To: <7ysmtrf74n.fsf@myxomop.com> (Alexander Kotelnikov's message of "Thu, 13 Mar 2003 13:34:16 -0500")
>>>>> On Thu, 13 Mar 2003 13:34:16 -0500, Alexander Kotelnikov
>>>>> <sacha@myxomop.com> said:
> This also means that "total" described as dangerous is not too much
> more dangerous than "auto", isn't it?
Well I don't think that we should say that auto-expire is for wimps,
but at least with auto-expire it's very explicitly clear to the user
that an article is marked expireable and that the user must take some
action if s/he doesn't want it to be. Moreover if using total-expire
and a tick or dormant mark (which are not total-expired) is
inadvertently removed and expiry takes place, the article will be
lost. That is not an issue for auto-expire. I therefore think
total-expire is more dangerous than auto-expire.
> So it can be advised to use total with adaptive scoring and auto
> otherwise. At first approximation they are the same.
In spite of being bitten by the problems described I use and prefer
total-expire in most of my groups. I really like adaptive scoring.
And I've got very good backups.
--
Dave Goldberg
david.goldberg6@verizon.net
next prev parent reply other threads:[~2003-03-13 18:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-13 14:50 Alexander Kotelnikov
2003-03-13 17:25 ` Kai Großjohann
2003-03-13 18:34 ` Alexander Kotelnikov
2003-03-13 18:54 ` David S Goldberg [this message]
2003-03-13 19:17 ` Kai Großjohann
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=u8zvfyn14iy.fsf@verizon.net \
--to=david.goldberg6@verizon.net \
/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).