From: "Devon H. O'Dell " <dodell@offmyserver.com>
To: 9fans@cse.psu.edu
Subject: [9fans] Kernel interface manpages
Date: Sat, 26 Mar 2005 09:36:29 +0100 [thread overview]
Message-ID: <20050326083629.GH93332@smp500.sitetronics.com> (raw)
In-Reply-To: <20050326083044.GG93332@smp500.sitetronics.com>
[-- Attachment #1: Type: text/plain, Size: 444 bytes --]
Ok, so spawning from my recent questions from the list, it
appears that we'd probably benefit from some concise, well
written man pages for kernel interfaces. I know Inferno has
(some of?) these, but as with addclock0link, ours does differ.
I'd be willing to write some extra man pages for kernel
interfaces. What'd be the best way to go about doing this?
Simply read through the {port}fns.h and write?
Should I do this?
--Devon
[-- Attachment #2: Type: application/pgp-signature, Size: 194 bytes --]
next prev parent reply other threads:[~2005-03-26 8:36 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-24 15:08 Fwd: [9fans] Ad link Brantley Coile
2005-03-24 15:54 ` Ronald G. Minnich
2005-03-24 21:15 ` Sam
2005-03-24 22:31 ` Ronald G. Minnich
2005-03-24 22:47 ` Russ Cox
2005-03-25 15:34 ` Brantley Coile
2005-03-26 0:00 ` geoff
2005-03-26 0:19 ` Russ Cox
2005-03-27 19:03 ` Fwd: " McLone
2005-03-25 4:39 ` geoff
2005-03-25 9:02 ` vdharani
2005-03-25 18:36 ` [9fans] tsleep / timer questions Devon H. O'Dell
2005-03-25 18:55 ` jmk
2005-03-25 20:19 ` Devon H. O'Dell
2005-03-25 18:57 ` Russ Cox
2005-03-25 20:04 ` Devon H. O'Dell
2005-03-25 20:12 ` Russ Cox
2005-03-25 20:23 ` Devon H. O'Dell
2005-03-25 21:36 ` Russ Cox
2005-03-26 8:30 ` Devon H. O'Dell
2005-03-26 8:36 ` Devon H. O'Dell [this message]
2005-03-26 17:45 ` [9fans] Kernel interface manpages Russ Cox
2005-03-26 19:56 ` Devon H. O'Dell
2005-03-26 23:03 ` vdharani
2005-03-26 0:22 ` [9fans] tsleep / timer questions vdharani
2005-03-25 8:51 ` Fwd: [9fans] Ad link vdharani
2005-03-25 15:27 ` Brantley Coile
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=20050326083629.GH93332@smp500.sitetronics.com \
--to=dodell@offmyserver.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).