From: Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann)
Subject: Re: Score on thread?
Date: Mon, 25 Jun 2001 22:22:17 +0200 [thread overview]
Message-ID: <vafu214ia2u.fsf@lucy.cs.uni-dortmund.de> (raw)
In-Reply-To: <vaflmmioz2d.fsf@lucy.cs.uni-dortmund.de> (Kai.Grossjohann@CS.Uni-Dortmund.DE's message of "Sun, 24 Jun 2001 14:13:46 +0200")
On Sun, 24 Jun 2001, Kai Großjohann wrote:
> I'm no scoring expert. In a German newsgroup about news readers,
> people said that Forté Agent can do better scoring on threads than
> Gnus, because Gnus only looks at the References headers of the
> articles, whereas Agent builds the thread tree first, then scores in
> that tree.
It turns out that there is the following in the Gnus info file:
/----[ Score File Format ]
| "Thread"
| This match key works along the same lines as the
| `Followup' match key. If you say that you want to score
| on a (sub-)thread started by an article with a
| `Message-ID' X, then you add a `thread' match. This
| will add a new `thread' match for each article that has
| X in its `References' header. (These new `thread'
| matches will use the `Message-ID's of these matching
| articles.) This will ensure that you can raise/lower
| the score of an entire thread, even though some articles
| in the thread may not have complete `References'
| headers. Note that using this may lead to
| undeterministic scores of the articles in the thread.
| (Using this match key will lead to creation of `ADAPT'
| files.)
\----
I think this means that Gnus is as smart as Agent. Right?
kai
--
~/.signature: No such file or directory
next parent reply other threads:[~2001-06-25 20:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <vaflmmioz2d.fsf@lucy.cs.uni-dortmund.de>
2001-06-25 20:22 ` Kai Großjohann [this message]
2001-08-19 20:29 ` Lars Magne Ingebrigtsen
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=vafu214ia2u.fsf@lucy.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).