From: "Russ Cox" <rsc@plan9.bell-labs.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] 9 in the news
Date: Sat, 21 Sep 2002 10:52:43 -0400 [thread overview]
Message-ID: <389925869064fef84ecf79afbc6adb51@plan9.bell-labs.com> (raw)
> Is it just me, or were the responses surprisingly uninformed?
It's hard to be surprised at the uninformedness of
a Slashdot discussion. Still, it was impressive to
me that no one understood what single sign-on
really meant. Everyone had the Microsoft version
stuck in their heads.
Russ
next reply other threads:[~2002-09-21 14:52 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-21 14:52 Russ Cox [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-09-23 14:38 Anssi Porttikivi
2002-09-21 20:28 Geoff Collyer
2002-09-23 14:13 ` Peter Downs
2002-09-23 16:00 ` Jack Johnson
2002-09-21 15:35 rob pike, esq.
2002-09-21 16:33 ` Jack Johnson
2002-09-21 17:17 ` matt
2002-09-22 22:22 ` Dan Cross
2002-09-21 14:39 anothy
2002-09-21 2:01 matt
2002-09-21 11:16 ` Lucio De Re
2002-09-21 15:21 ` Arnaud SAHUGUET
2002-09-21 15:57 ` Jack Johnson
2002-09-21 16:01 ` Ronald G Minnich
2002-09-21 21:55 ` Steve Kilbane
2002-10-01 12:45 ` matt
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=389925869064fef84ecf79afbc6adb51@plan9.bell-labs.com \
--to=rsc@plan9.bell-labs.com \
--cc=9fans@cse.psu.edu \
/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).