From: john@csplan9.rit.edu
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Re: You might enjoy this
Date: Tue, 5 Jun 2007 08:39:09 -1000 [thread overview]
Message-ID: <96af50fcdf1d01fe95ca8ab0630a572c@csplan9.rit.edu> (raw)
In-Reply-To: <14ec7b180706051129w28dcb8efy55e55eba65ec6ca6@mail.gmail.com>
> come on you two, i was throwing a jab at this sentence from the abstract:
>
> "Why are so many existing systems architecturally undistinguished, and
> what can we do to improve them?"
Good god, man, engineers/programmers reading? You must have different
standards.</jest>
John "I'll Read It Later" Floren
next prev parent reply other threads:[~2007-06-05 18:39 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200706051447.l55El0ma028778@sparkle.iba.co.za>
2007-06-05 17:52 ` lucio
2007-06-05 18:03 ` andrey mirtchovski
2007-06-05 18:08 ` lucio
2007-06-05 18:24 ` Sape Mullender
2007-06-05 18:29 ` andrey mirtchovski
2007-06-05 18:39 ` john [this message]
2007-06-05 18:55 ` Bakul Shah
2007-06-05 19:46 ` Skip Tavakkolian
2007-06-05 20:02 ` W B Hacker
2007-06-05 21:34 ` Gregory Pavelcak
2007-06-05 21:50 ` erik quanstrom
2007-06-05 22:46 ` W B Hacker
2007-06-05 23:00 ` W B Hacker
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=96af50fcdf1d01fe95ca8ab0630a572c@csplan9.rit.edu \
--to=john@csplan9.rit.edu \
--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).