From: "H. Peter Anvin" <hpa@transmeta.com>
To: "Albert D. Cahalan" <acahalan@cs.uml.edu>
Cc: "Maciej W. Rozycki" <macro@ds2.pg.gda.pl>,
Dunlap Randy <randy.dunlap@intel.com>,
"'H. Peter Anvin'" <hpa@zytor.com>,
linux-kernel@vger.kernel.org
Subject: Re: The latest instance in the A20 farce
Date: Mon, 15 Jan 2001 12:00:36 -0800 [thread overview]
Message-ID: <3A6356E4.4B5CFE01@transmeta.com> (raw)
In-Reply-To: <200101151930.f0FJUTC254802@saturn.cs.uml.edu>
"Albert D. Cahalan" wrote:
>
> It looks like we let Microsoft fill the design guide void.
> If you were to write "PC DESIGN GUIDE - For the Linux Operating
> System" and a pile of test code, then there would be an
> alternative to point people at.
>
> Complaining is pretty useless.
I was thinking about this today. If we write a Linux design guide, even
as a delta spec, does anyone think it will be listed to?
-hpa
--
<hpa@transmeta.com> at work, <hpa@zytor.com> in private!
"Unix gives you enough rope to shoot yourself in the foot."
http://www.zytor.com/~hpa/puzzle.txt
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2001-01-15 20:01 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-10 23:56 The latest instance in the A20 farce Dunlap, Randy
2001-01-11 0:09 ` H. Peter Anvin
2001-01-11 10:32 ` Olaf Titz
2001-01-15 17:24 ` Maciej W. Rozycki
2001-01-15 17:44 ` H. Peter Anvin
2001-01-15 19:30 ` Albert D. Cahalan
2001-01-15 20:00 ` H. Peter Anvin [this message]
2001-01-18 12:21 ` Gerhard Mack
-- strict thread matches above, loose matches on Subject: below --
2001-01-11 1:43 Dunlap, Randy
2001-01-11 1:59 ` H. Peter Anvin
2000-12-06 23:55 H. Peter Anvin
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=3A6356E4.4B5CFE01@transmeta.com \
--to=hpa@transmeta.com \
--cc=acahalan@cs.uml.edu \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=macro@ds2.pg.gda.pl \
--cc=randy.dunlap@intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.