From: Jody <jbruchon@nc.rr.com>
To: Linux-8086 <linux-8086@vger.kernel.org>
Subject: ELKS Website Fixer-Upper
Date: Tue, 02 May 2006 09:05:51 -0400 [thread overview]
Message-ID: <4457592F.3000602@nc.rr.com> (raw)
Well, everyone, it looks like I have everything short of admin
privileges now, so I'll see what I can do about cleaning up this mess
over the next couple of weeks. Feel free to shoot any kind of
suggestions you may have about the website my way. The first two things
that I think would be appropriate to do is to actually release "ELKS
0.1.3" that never was released in a tarball, and throw up a small
memorial page for the late RHW.
Anything else?
Jody
next reply other threads:[~2006-05-02 13:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-02 13:05 Jody [this message]
2006-05-02 13:53 ` ELKS Website Fixer-Upper Hans
2006-05-02 14:03 ` Alan Cox
2006-05-02 19:51 ` Segin
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=4457592F.3000602@nc.rr.com \
--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