From: Jonathan Larmour <jifl@eCosCentric.com>
To: eCos Maintainers <ecos-maintainers@ecos.sourceware.org>
Subject: EL/IX
Date: Mon, 10 Mar 2008 10:29:00 -0000 [thread overview]
Message-ID: <47D50D76.4020608@eCosCentric.com> (raw)
The sourceware overseers are agitating for removing the EL/IX project since
it's extremely dead. They have a point.
http://sourceware.org/elix/
However we refer to it in a few places from our docs.
Should I either:
1) object entirely?
2) Incorporate the EL/IX spec into the eCos project?
or
3) Just remove all our EL/IX references.
Personally I think 3. It's time to just face up to the fact it's dead.
Jifl
--
eCosCentric Limited http://www.eCosCentric.com/ The eCos experts
** Visit us at ESC Silicon Valley <http://www.embedded.com/esc/sv> **
** April 15-17 2008, Booth 3012, San Jose McEnery Convention Center **
Barnwell House, Barnwell Drive, Cambridge, UK. Tel: +44 1223 245571
Registered in England and Wales: Reg No 4422071.
------["Si fractum non sit, noli id reficere"]------ Opinions==mine
next reply other threads:[~2008-03-10 10:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-10 10:29 Jonathan Larmour [this message]
2008-03-10 10:36 ` EL/IX Andrew Lunn
2008-03-10 10:57 ` EL/IX Gary Thomas
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=47D50D76.4020608@eCosCentric.com \
--to=jifl@ecoscentric.com \
--cc=ecos-maintainers@ecos.sourceware.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).