From: Jody Bruchon <jody@jodybruchon.com>
To: ELKS <linux-8086@vger.kernel.org>
Subject: ELKS SourceForge website is fixed up
Date: Sun, 22 Mar 2015 13:49:59 -0400 [thread overview]
Message-ID: <550F00C7.9030808@jodybruchon.com> (raw)
I've updated the ELKS website. It's not completely up-to-date (I really
don't have time to fiddle with the FAQs, for example) but the home page,
mailing list page, and download page have been corrected. The front page
should point people where they really need to be, the "news" has been
pushed to a link at the top and renamed to make it clear that it's an
archive only, and "download" now just says "go to GitHub" instead of
providing a plethora of broken links.
If anyone has any other suggestions while I'm in here doing the edits,
please chip in ASAP. I'm not going to spend much more time on it.
I've also asked Bernhard (a uClibc maintainer) to update the links to
ELKS in the historical information on the uClibc FAQ, and he has said he
will update them sometime next week. The ELKS Wikipedia page links and
information also appear to have been corrected. If you know of other
dead links to ELKS (such as the "cix" or "soton" ones) that are still
floating around out there, please ask the maintainers of those sites to
correct the links.
Pointing to the SourceForge ELKS site should be okay since it basically
says "go to GitHub" but the GitHub repo is really the best resource
right now for someone who's interested in ELKS.
-Jody
next reply other threads:[~2015-03-22 17:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-22 17:49 Jody Bruchon [this message]
2015-03-23 0:39 ` ELKS SourceForge website is fixed up Royce Williams
2015-03-23 7:54 ` MFLD
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=550F00C7.9030808@jodybruchon.com \
--to=jody@jodybruchon.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).