From: "ron minnich" <rminnich@gmail.com>
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@cse.psu.edu>
Subject: [9fans] New IBM chip to allow faster downlaids -- news headline
Date: Thu, 12 Apr 2007 08:17:51 -0700 [thread overview]
Message-ID: <13426df10704120817n3a988ec5k4ec2219bcb628ccf@mail.gmail.com> (raw)
on reading this headline, one thinks --
1. written by underpaid, lonely intern
2. spell check is over-trusted
3. this ought to bring more people into the CS business
4. so, exactly which devices will this chip be used in?
5. written by a victim of outsourcing on last day of employment
More typos I got a kick out of recently.
"We don't want undo risk" -- well, actually, I think you would want to undo risk
"We must not do anything that would effect security" -- Whew! I can
handle that assignment.
thanks
ron
reply other threads:[~2007-04-12 15:17 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=13426df10704120817n3a988ec5k4ec2219bcb628ccf@mail.gmail.com \
--to=rminnich@gmail.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).