From: Brantley Coile <brantley@coraid.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] [OT] URI
Date: Fri, 21 Apr 2006 10:47:18 -0400 [thread overview]
Message-ID: <3e08685d74af9402b840e9367d3224d3@coraid.com> (raw)
In-Reply-To: <Pine.BSO.4.63.0604211114340.2357@wodka.lkn.ei.tum.de>
> I found
> Computer Organization and Design. The Hardware/Software Interface. by
> David A. Patterson, John L. Hennessy
The two books by Patterson and Hennessy are just a couple of exceptions
to the `large id bad' generalizations, not that you mention them. I even
find one or the other of them in my local Borders book store.
next prev parent reply other threads:[~2006-04-21 14:47 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-20 1:41 [9fans] Install from CD fails erik quanstrom
2006-04-20 6:17 ` Charles Forsyth
2006-04-20 6:35 ` [9fans] [OT] URI Charles Forsyth
2006-04-20 6:53 ` geoff
2006-04-20 15:01 ` Brantley Coile
2006-04-20 15:32 ` Paul Lalonde
2006-04-20 15:49 ` Brantley Coile
2006-04-20 16:04 ` Paul Lalonde
2006-04-20 16:47 ` Jack Johnson
2006-04-21 9:22 ` Moritz Kiese
2006-04-21 14:47 ` Brantley Coile [this message]
2006-04-21 4:54 ` quanstro
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=3e08685d74af9402b840e9367d3224d3@coraid.com \
--to=brantley@coraid.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).