From: "Ted Zlatanov" <tzz@lifelogs.com>
Subject: Re: recheck arguments for commands to display spamicity scores
Date: 14 May 2004 15:28:01 -0400 [thread overview]
Message-ID: <4niseykdvi.fsf@lifelogs.com> (raw)
In-Reply-To: <87isfhbijn.fsf@namazu.org> (TSUCHIYA Masatoshi's message of "Sat, 01 May 2004 00:18:52 +0900")
On Sat, 01 May 2004, tsuchiya@namazu.org wrote:
> I have added an optional argument `recheck', to
> `spam-generic-score', `spam-bogofilter-score' and
> `spam-spamassassin-score'.
I'm not sure I understand exactly what you're doing, the diff says
you're removing the "recheck" argument.
> And more, I'd like to propose the patch attached at the last of this
> message, to change their default actions, because old spamicity
> scores kept by headers must be less important than ones calculated
> using the current updated database, when using spam detector based
> on headers, including `spam-use-bogofilter-headers'.
>
> Can I commit this change?
I think the goal is good, can you check that your patch is correct
though? I may be confused too easily :)
Ted
prev parent reply other threads:[~2004-05-14 19:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-30 15:18 TSUCHIYA Masatoshi
2004-05-14 19:28 ` Ted Zlatanov [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=4niseykdvi.fsf@lifelogs.com \
--to=tzz@lifelogs.com \
/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).