From: Segin <segin2005@gmail.com>
To: Jody <jbruchon@nc.rr.com>
Cc: Linux-8086 <linux-8086@vger.kernel.org>
Subject: Re: ELKS Website Fixer-Upper
Date: Tue, 02 May 2006 15:51:48 -0400 [thread overview]
Message-ID: <4457B854.1010608@gmail.com> (raw)
In-Reply-To: <4457592F.3000602@nc.rr.com>
Jody wrote:
> 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
> -
> 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
>
I have a wonderful idea, listen:
We collect our late friend's emails sent to this newsgroup on ELKS. Put
them into a random message generator, and make a fortune page with
edited emails, semi-edited emails, unedited emails, unedited quotes, and
edited quotes. The emails bit is easy, just a matter of collecting them
from the archive, the quotes is where we look at the emails, and take
our our trusty yellow highlighter and select the best (and worst) of
RHW's quotes.
Sounds like a nice memberance, don't you agree?
--
The real problem with C++ for kernel modules is: the language just sucks.
-- Linus Torvalds
prev parent reply other threads:[~2006-05-02 19:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-02 13:05 ELKS Website Fixer-Upper Jody
2006-05-02 13:53 ` Hans
2006-05-02 14:03 ` Alan Cox
2006-05-02 19:51 ` Segin [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=4457B854.1010608@gmail.com \
--to=segin2005@gmail.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