From: Peter Korsgaard <jacmet@sunsite.dk>
To: ecos-devel@ecos.sourceware.org
Subject: New release?
Date: Sun, 22 May 2005 16:05:00 -0000 [thread overview]
Message-ID: <87acmnw8ht.fsf@p4.48ers.dk> (raw)
Hi,
As the eCos 2.0 release is turning 2 years this weekend
(http://ecos.sourceware.org/ml/ecos-announce/2003/msg00005.html), I
was wondering if it wasn't about time with a new release?
A new release would give some nice publicity and hopefully stop people
from wasting time on the ancient v2.0 release, only to later discover
that it was fixed long time ago in CVS.
But what is the status?
It would be nice if the Redhat->FSF assignment could be completed
before the release, but that doesn't seem to be happening?
What about the flash v2 API? Is that getting ready for public
consumption?
Other significant changes since v2.0:
* HAL: A bunch of new platforms
* NET: SNTP, PPP, Improved IPv6 support, IPSEC, LwIP, VNC
* IO: IDE, NAND flash, SPI, I2C
* FS: FAT12/16
..
--
Bye, Peter Korsgaard
next reply other threads:[~2005-05-22 16:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-22 16:05 Peter Korsgaard [this message]
2005-05-25 14:56 ` Jonathan Larmour
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=87acmnw8ht.fsf@p4.48ers.dk \
--to=jacmet@sunsite.dk \
--cc=ecos-devel@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).