From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@cse.psu.edu, Brantley Coile <brantley@coraid.com>
Subject: Re: [9fans] GNU binutils: you can't make this stuff up
Date: Thu, 19 Jan 2006 16:24:40 -0600 [thread overview]
Message-ID: <20060119222440.0AEFA1140E1@dexter-peak.quanstro.net> (raw)
In-Reply-To: <a4cdcf6246d06f7445473b9c35c1a614@coraid.com>
what does unicode have to do with compiler design?
does "microkernel" mean anything specific? i'm not convinced that it does.
- erik
Brantley Coile <brantley@coraid.com> writes
|
| Microkernels are to OS design what Unicode was to compiler design.
next prev parent reply other threads:[~2006-01-19 22:24 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-16 1:50 [9fans] GNU binutils: you can't make this shit up Ronald G Minnich
2006-01-16 2:00 ` Andy Newman
2006-01-16 3:10 ` Ronald G Minnich
2006-01-16 3:19 ` erik quanstrom
2006-01-16 3:47 ` David Leimbach
2006-01-18 12:55 ` Eirik Johnson
2006-01-18 13:45 ` Bruce Ellis
2006-01-18 14:00 ` alexandr babic
2006-01-18 15:45 ` Ronald G Minnich
2006-01-18 16:45 ` Bruce Ellis
2006-01-18 17:00 ` alexandr babic
2006-01-18 17:04 ` Bruce Ellis
2006-01-18 17:00 ` David Leimbach
2006-01-18 17:14 ` Ronald G Minnich
2006-01-19 8:29 ` Eirik Johnson
2006-01-19 10:34 ` Charles Forsyth
2006-01-19 10:43 ` Bruce Ellis
2006-01-19 10:46 ` erik quanstrom
2006-01-19 10:52 ` Bruce Ellis
2006-01-19 15:41 ` Ronald G Minnich
2006-01-19 16:05 ` David Leimbach
2006-01-19 16:15 ` [9fans] GNU binutils: you can't make this stuff up Brantley Coile
2006-01-19 17:16 ` Bruce Ellis
2006-01-19 22:24 ` erik quanstrom [this message]
2006-01-16 17:43 ` [9fans] GNU binutils: you can't make this shit up Ronald G Minnich
2006-01-16 3:46 ` David Leimbach
2006-01-16 17:44 ` Ronald G Minnich
2006-01-16 19:09 ` Bruce Ellis
2006-01-16 7:48 ` Andy Newman
2006-01-16 9:08 ` Bruce Ellis
2006-01-16 12:06 ` erik quanstrom
2006-01-16 13:23 ` Bruce Ellis
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=20060119222440.0AEFA1140E1@dexter-peak.quanstro.net \
--to=quanstro@quanstro.net \
--cc=9fans@cse.psu.edu \
--cc=brantley@coraid.com \
/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).