From: Stanislav Meduna <stano@meduna.org>
To: ecos-discuss@ecos.sourceware.org
Subject: Re: [ECOS] ecos project still alive?
Date: Fri, 23 Jun 2017 23:35:00 -0000 [thread overview]
Message-ID: <d17ee2b2-95a3-0c8f-0853-ec6360f0e5a9@meduna.org> (raw)
In-Reply-To: <b6499943-74a2-ad18-d1f1-3aebea471676@gmx.de>
On 23.6.2017 18:57, PicassoCT wrote:
> Many successful and completed projects are in maintenance mode.
Having one network stack (BSD) from 2002 and another (lwIP)
from 2009 does not look like a maintenance mode to me.
It could well be that the eCosPro lives. This is however in
a price range where there are several alternatives to explore.
I completely respect the eCosCentric's decision not to move
forward with the public version, but as a free OS I'm afraid
the eCos is dead, as there is obviously no relevant community
to contribute.
--
Stano
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
prev parent reply other threads:[~2017-06-23 23:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-23 11:25 15802542327
2017-06-23 15:41 ` [ECOS] " Grant Edwards
2017-06-23 16:45 ` Alex Schuilenburg
2017-06-23 23:27 ` Grant Edwards
2017-06-23 16:58 ` [ECOS] " PicassoCT
2017-06-23 23:35 ` Stanislav Meduna [this message]
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=d17ee2b2-95a3-0c8f-0853-ec6360f0e5a9@meduna.org \
--to=stano@meduna.org \
--cc=ecos-discuss@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).