From: Thomas Skogestad <tskogest@jusstud.uio.no>
Subject: Re: What happened to Xref scoring? (was all.SCORE?)
Date: 09 May 2001 20:21:31 +0200 [thread overview]
Message-ID: <3198421291138560@oakhurst.yi.org> (raw)
In-Reply-To: <3198308041038906@oakhurst.yi.org>
* Thomas Skogestad
| 5.8.7 loves it, while 5.8.8 and Oort just ignores it.
(Bzzt! Wrong!) not a problem with all.SCORE, but...
The error however seems to be parsing of the Xref header. Does not seem to
work in newer Gnusae.
Now I must see all of this massively cross-posted spam junk.
And why does the CVS Oort force you to obey the followup-to header? I want
some control over where I post.
--
thomas.skogestad@jusstud.uio.no
http://quimby.gnus.org/circus/problem.gif
http://www.messengers-of-messiah.org/~csebold/emacs/why.phtml
next prev parent reply other threads:[~2001-05-09 18:21 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-08 10:54 What happened to all.SCORE? Thomas Skogestad
2001-05-09 18:21 ` Thomas Skogestad [this message]
2001-05-09 18:26 ` What happened to Xref scoring? (was all.SCORE?) Paul Jarc
2001-05-09 19:12 ` Paul Jarc
2001-05-09 23:40 ` Steve Youngs
2001-05-10 8:32 ` Thomas Skogestad
2001-05-12 13:15 ` Steve Youngs
2001-05-10 15:07 ` Robin S. Socha
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=3198421291138560@oakhurst.yi.org \
--to=tskogest@jusstud.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).