From: Karl Kleinpaste <karl@jprc.com>
Subject: Re: Inexplicable all.SCORE analysis
Date: 24 Sep 1997 11:20:39 -0400 [thread overview]
Message-ID: <vxkzpp2kabc.fsf@pocari-sweat.jprc.com> (raw)
In-Reply-To: Lars Magne Ingebrigtsen's message of "24 Sep 1997 01:58:58 +0200"
Lars Magne Ingebrigtsen <larsi@gnus.org> writes:
> Currently Gnus uses everything in the last slot as the Xref header.
> Which means that you have a very long one.
(*sigh* I suppose I should have expected that.)
No, it doesn't, in my case, as I've got a patch to handle Keywords: in
overviews, auto-generated by INN (a patch I wrote for $inn/innd/art.c,
which is now part of 1.6bN). For a contrary example, the article
showing this overview does not score-down on a misguided Xref: analysis.
435 US-PA-PGH-Records Management Systems Consultant nescopgh@nauticom.net (NESCO Technical Services) 22 Sep 1997 21:58:19 GMT <606plr$5ac@news.psc.edu> 3341 66 Xref: news.jprc.com pgh.jobs.offered:435 Keywords: management nesco document company systems page consultant experience pittsburgh service please resume home http mail plus www manufacturing assignment technical nauticom nescopgh services records windows timing visit wish faq fax net implementation compensation construction nescoservice organization experienced information knowledable monroeville opportunity confidence responding specifying technology candidate computing corporate deploying designing expertise immediate important 101
This item scores up via the local scorefile, and doesn't trip the xref
entry in all.SCORE. The total *Score Trace* buffer for this article:
("pitt\\|pgh" nil nil r) -> SCORE
Anyhow, something else funny is going on, and I'll chase it down somehow.
next prev parent reply other threads:[~1997-09-24 15:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
1997-09-23 18:29 Karl Kleinpaste
1997-09-23 21:38 ` SL Baur
1997-09-23 23:58 ` Lars Magne Ingebrigtsen
1997-09-24 15:20 ` Karl Kleinpaste [this message]
1997-09-24 22:17 ` Lars Magne Ingebrigtsen
1997-09-25 1:23 ` SPCs can hurt overviews (was Inexplicable all.SCORE analysis) Karl Kleinpaste
1997-09-27 3:35 ` 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=vxkzpp2kabc.fsf@pocari-sweat.jprc.com \
--to=karl@jprc.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).