From: Jody <jbruchon@nc.rr.com>
To: ELKS <linux-8086@vger.kernel.org>
Subject: Site updated
Date: Tue, 09 May 2006 03:56:01 -0400 [thread overview]
Message-ID: <44604B11.5070400@nc.rr.com> (raw)
I have completed an update of the ELKS website. Some of the content on
the site was unnecessary, and such content was removed.
http://elks.sourceforge.net/
As always, stay tuned for more fun developments. I still haven't
figured out why bcc's cpp is kicking #includes around on elkscmd.
Jody
next reply other threads:[~2006-05-09 7:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-09 7:56 Jody [this message]
2006-05-09 9:18 ` Site updated jb1
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=44604B11.5070400@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.