From: David Leimbach <leimy2k@gmail.com>
To: Rob Pike <robpike@gmail.com>,
Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] plumbopen too smart?
Date: Thu, 13 Jan 2005 23:47:54 -0800 [thread overview]
Message-ID: <3e1162e60501132347b85418d@mail.gmail.com> (raw)
In-Reply-To: <7359f049050113233715806c3f@mail.gmail.com>
On Thu, 13 Jan 2005 23:37:46 -0800, Rob Pike <robpike@gmail.com> wrote:
> If you feel this way, don't read the code for the cpu command.
>
> -rob
>
Don't hit him too hard :). He just did a port to Sparc64.
It's probably my fault. I started this whole discussion as a newbie
playing around with cpu and looking at what's going on with plumber
and asking too many questions.
- Dave
next prev parent reply other threads:[~2005-01-14 7:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-14 5:45 Tim Newsham
2005-01-14 7:37 ` Rob Pike
2005-01-14 7:47 ` David Leimbach [this message]
2005-01-14 8:12 ` Sam
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=3e1162e60501132347b85418d@mail.gmail.com \
--to=leimy2k@gmail.com \
--cc=9fans@cse.psu.edu \
--cc=robpike@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).