From: "Riley Williams" <Riley@Williams.Name>
To: Stefan de Konink <skinkie@xs4all.nl>
Cc: Linux ELKS <Linux-8086@vger.kernel.org>
Subject: RE: ELKS Website - version 2
Date: Fri, 18 Jul 2003 01:15:17 +0100 [thread overview]
Message-ID: <BKEGKPICNAKILKJKMHCAGEPPEOAA.Riley@Williams.Name> (raw)
In-Reply-To: <20030718005612.S15757-100000@xs2.xs4all.nl>
Hi Stefan.
>> For those interested, the proposed version 2 of the ELKS website,
>> which is aimed to automatically use the surfer's preferred choice
>> of language, has been loaded at...
>>
>> http://elks.sf.net/2/
>>
>> ...for those interested. It clearly needs LOTS of work before it
>> is ready for mainline though...
> Was this my v2 your are using at /2 because there a lot of errors...
That's the elksweb2 package on the CVS server. If that corresponds to
your v2 then yes, it is. Since the normal website is simply the
elksweb (without the '2' suffix) extracted into the relevant directory
I just did the same with the elksweb2 package.
Those errors are the reason for my saying it clearly needs LOTS of work
before it's ready for mainline, and that's also why it isn't linked to
from the current website.
Best wishes from Riley.
---
* Nothing as pretty as a smile, nothing as ugly as a frown.
---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.501 / Virus Database: 299 - Release Date: 14-Jul-2003
next prev parent reply other threads:[~2003-07-18 0:15 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-17 22:44 ELKS Website - version 2 Riley Williams
2003-07-17 22:57 ` Stefan de Konink
2003-07-18 0:15 ` Riley Williams [this message]
2003-07-18 8:38 ` Phil Goembel
2003-07-18 18:35 ` Riley Williams
2003-07-19 0:23 ` Phil Goembel
2003-07-19 1:11 ` Phil Goembel
2003-07-17 23:40 ` Harry Kalogirou
2003-07-18 0:28 ` Riley Williams
-- strict thread matches above, loose matches on Subject: below --
2003-07-18 10:38 Stefan de Konink
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=BKEGKPICNAKILKJKMHCAGEPPEOAA.Riley@Williams.Name \
--to=riley@williams.name \
--cc=Linux-8086@vger.kernel.org \
--cc=skinkie@xs4all.nl \
/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