From: "Robin S. Socha" <robin@socha.net>
Subject: Re: What happened to Xref scoring? (was all.SCORE?)
Date: 10 May 2001 17:07:34 +0200 [thread overview]
Message-ID: <deathsquad.m3n18lw8cp.fsf@socha.net> (raw)
In-Reply-To: <microsoft-free.x4heyu5bwk.fsf@slackware.mynet.pc> (Steve Youngs's message of "10 May 2001 09:40:43 +1000")
* Steve Youngs <youngs@xemacs.org> writes:
> Thomas Skogestad <tskogest@jusstud.uio.no> writes:
>> And why does the CVS Oort force you to obey the followup-to header?
>> I want some control over where I post.
> Although control over what you do is a good thing, why do you want to
> ignore your reader's wishes?
Reader? How about "boys trying to be men" aka MCSEs running mailing lists?
--
Robin S. Socha <http://my.gnus.org/users/robin/>
http://my.gnus.org/ - To boldly frobnicate what no newbie has grokked before.
prev parent reply other threads:[~2001-05-10 15:07 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 ` What happened to Xref scoring? (was all.SCORE?) Thomas Skogestad
2001-05-09 18:26 ` 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 [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=deathsquad.m3n18lw8cp.fsf@socha.net \
--to=robin@socha.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).