From: "ron minnich" <rminnich@gmail.com>
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@cse.psu.edu>
Subject: Re: [9fans] Consindering eBox-4854 for Plan9
Date: Fri, 15 Feb 2008 10:51:13 -0800 [thread overview]
Message-ID: <13426df10802151051w531f272ej9e98f773ce34df0d@mail.gmail.com> (raw)
In-Reply-To: <197d3c76b316d8e3c64b5cc4faae75ba@quanstro.net>
On Fri, Feb 15, 2008 at 10:47 AM, erik quanstrom <quanstro@quanstro.net> wrote:
> actually programming documentation or just code?
just code, but, while I realize code alone is often useless, I am
willing to bet the docs in this case are less useful than code. The
code will have all the huge doc gaps filled in.
ron
next prev parent reply other threads:[~2008-02-15 18:51 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-15 9:51 TheAbysmal
2008-02-15 12:38 ` erik quanstrom
2008-02-15 18:39 ` ron minnich
2008-02-15 18:47 ` erik quanstrom
2008-02-15 18:51 ` ron minnich [this message]
2008-02-15 18:56 ` erik quanstrom
2008-02-15 19:01 ` ron minnich
2008-02-15 19:16 ` erik quanstrom
2008-02-15 21:09 ` John Barham
2008-02-15 21:16 ` John Barham
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=13426df10802151051w531f272ej9e98f773ce34df0d@mail.gmail.com \
--to=rminnich@gmail.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).