From: "Jody" <jbruchon@nc.rr.com>
To: Linux-8086 <linux-8086@vger.kernel.org>
Subject: Documentation
Date: Sat, 15 May 2004 10:28:53 -0400 [thread overview]
Message-ID: <001601c43a88$f2df9a00$0101a8c0@vash> (raw)
I feel that with the recent activity concerning ELKS, I should extend my
offer to make up any kind of documentation that I can for the project,
since this is the weakest link in most projects. I am NOT a programmer,
and I am not an expert at compiling and porting. I can document anything
that anyone can help me reproduce at my house that needs to have
documentation for the ELKS project to see more activity. If anyone has any
ideas what I can go about documenting, please email me back or look for
"nsx" in the #elks IRC channel.
Jody
next reply other threads:[~2004-05-15 14:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-15 14:28 Jody [this message]
2004-05-17 13:35 ` Documentation Andrey Romanenko
2004-05-17 13:40 ` Documentation Miguel Bolanos
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='001601c43a88$f2df9a00$0101a8c0@vash' \
--to=jbruchon@nc.rr.com \
--cc=linux-8086@vger.kernel.org \
/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