From: Boyd Roberts <boyd@strakt.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] dhog the corruptor!
Date: Fri, 16 Nov 2001 12:56:45 +0100 [thread overview]
Message-ID: <3BF4FEFD.293CF454@strakt.com> (raw)
In-Reply-To: <20011114092608.DE3CE19A27@mail.cse.psu.edu>
forsyth@vitanuova.com wrote:
> it's less of a problem for device drivers because they have a
> narrow interface that doesn't change too often. it does change, though:
> ulong one year, vlong the next.
I don't see it as a problem. Remember cyntax(1)? brucee again.
next prev parent reply other threads:[~2001-11-16 11:56 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-14 9:26 forsyth
2001-11-16 11:56 ` Boyd Roberts [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-11-13 23:54 forsyth
2001-11-13 23:53 David Gordon Hogan
2001-11-13 23:50 David Gordon Hogan
2001-11-14 0:34 ` Quinn Dunkan
2001-11-14 4:46 ` Lucio De Re
2001-11-16 11:52 ` Boyd Roberts
2001-11-13 23:04 David Gordon Hogan
2001-11-13 23:28 ` Quinn Dunkan
2001-11-13 23:38 ` Chris Hollis-Locke
2001-11-13 22:53 anothy
2001-11-13 22:59 ` George Michaelson
2001-11-13 22:32 David Gordon Hogan
2001-11-13 22:09 anothy
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=3BF4FEFD.293CF454@strakt.com \
--to=boyd@strakt.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).