From: Miguel Bolanos <mike@linuxlabs.com>
To: Jody <jbruchon@nc.rr.com>
Cc: Linux-8086 <linux-8086@vger.kernel.org>
Subject: Re: Documentation
Date: Mon, 17 May 2004 07:40:34 -0600 [thread overview]
Message-ID: <1084801234.3062.7.camel@talena.hsol.net> (raw)
In-Reply-To: <001601c43a88$f2df9a00$0101a8c0@vash>
Good Day Jody!
On Sat, 2004-05-15 at 08:28, Jody wrote:
> 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.
>
Thanks a lot for your offer.. actually as part of the new plan for
elks.. we will need to not only improve the current documentation, but
also write docs for the new kernel work plus gcc-8086 stuff.
Something that u have to be aware is that the community is not only
powered by Skilled coders, but also by people with a lot of will to help
on anything that they can as it is Doc writing.. so indeed, please
follow the work, and feel free to ask questions whether it is here or on
the list.
best wishes.
Mike
> Jody
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-8086" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
prev parent reply other threads:[~2004-05-17 13:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-15 14:28 Documentation Jody
2004-05-17 13:35 ` Documentation Andrey Romanenko
2004-05-17 13:40 ` Miguel Bolanos [this message]
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=1084801234.3062.7.camel@talena.hsol.net \
--to=mike@linuxlabs.com \
--cc=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