From: Grant Edwards <grant.b.edwards@gmail.com>
To: ecos-discuss@ecos.sourceware.org
Subject: [ECOS] Re: ecos project still alive?
Date: Fri, 23 Jun 2017 15:41:00 -0000 [thread overview]
Message-ID: <oijcqe$ekm$1@blaine.gmane.org> (raw)
In-Reply-To: <594CFA8F.5A21B5.01235@m15-112.126.com>
On 2017-06-23, 15802542327 <15802542327@126.com> wrote:
> last update has been than 2 years. is this project still alive?
That depends on your definition of "alive". It isn't really being
actively developed. I wouldn't use it for a new project, but it still
works well enough that I'm not looking to port my product firmware to
a different RTOS.
--
Grant Edwards grant.b.edwards Yow! Am I in GRADUATE
at SCHOOL yet?
gmail.com
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
next prev parent reply other threads:[~2017-06-23 15:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-23 11:25 [ECOS] " 15802542327
2017-06-23 15:41 ` Grant Edwards [this message]
2017-06-23 16:45 ` [ECOS] " Alex Schuilenburg
2017-06-23 23:27 ` Grant Edwards
2017-06-23 16:58 ` [ECOS] " PicassoCT
2017-06-23 23:35 ` Stanislav Meduna
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='oijcqe$ekm$1@blaine.gmane.org' \
--to=grant.b.edwards@gmail.com \
--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).