From: "boyd, rounin" <boyd@insultant.net>
To: "Russ Cox" <russcox@gmail.com>,
"Fans of the OS Plan 9 from Bell Labs" <9fans@cse.psu.edu>
Subject: Re: [9fans] Grap paper
Date: Mon, 6 Sep 2004 02:51:04 +0200 [thread overview]
Message-ID: <01a501c493ab$9a7f6f30$f5667d50@SOMA> (raw)
In-Reply-To: <ee9e417a040905174937c893fb@mail.gmail.com>
> We could, but it's not really a Plan 9 paper.
> Then we should put eqn and pic there and so on.
ahh, be buggered.
add a section entitled 'other resources' or something.
or just NATIVE port 'em.
next prev parent reply other threads:[~2004-09-06 0:51 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-05 21:10 Brantley Coile
2004-09-05 22:42 ` geoff
2004-09-05 22:45 ` Brantley Coile
2004-09-06 0:49 ` Russ Cox
2004-09-06 0:51 ` boyd, rounin [this message]
2004-09-06 1:05 Ben Huntsman
2004-09-06 12:12 ` Brantley Coile
2004-09-06 7:54 Aharon Robbins
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='01a501c493ab$9a7f6f30$f5667d50@SOMA' \
--to=boyd@insultant.net \
--cc=9fans@cse.psu.edu \
--cc=russcox@gmail.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).