From: John Dallaway <john@dallaway.org.uk>
To: abhishek srivastava <just_abhi22@yahoo.co.in>
Cc: "ecos-discuss@sourceware.org" <ecos-discuss@sourceware.org>
Subject: [ECOS] Re: is eCos dying?
Date: Sat, 03 Oct 2015 08:15:00 -0000 [thread overview]
Message-ID: <560F8EB4.4030304@dallaway.org.uk> (raw)
In-Reply-To: <349750926.354427.1443800101065.JavaMail.yahoo@mail.yahoo.com>
Hi Abhishek
eCos is not dying, but I would have to agree that there has been less
activity on the mailing lists recently.
John Dallaway
-------- Forwarded Message --------
Subject: is eCos dying?
Date: Fri, 2 Oct 2015 15:35:01 +0000 (UTC)
From: abhishek srivastava <just_abhi22@yahoo.co.in>
Reply-To: abhishek srivastava <just_abhi22@yahoo.co.in>
To: Ecos Discuss <ecos-discuss@sourceware.org>, John Dallaway
<john@dallaway.org.uk>
hi
I am interested to learn ecos for mbed LPC1768 or TI Tiva C
microcontroller but it seems very less activity on eCos.
Would it be worth to start learning on eCos or is it dying ?I have seen
enough activity in 2007 but now it is minimal this year.
Is it getting outdated? should i begin to work using eCos or should i
look for other alternative?\
Thank you
Abhishek
--
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 parent reply other threads:[~2015-10-03 8:15 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <349750926.354427.1443800101065.JavaMail.yahoo@mail.yahoo.com>
2015-10-03 8:15 ` John Dallaway [this message]
2015-10-04 8:30 ` Stanislav Meduna
2015-10-04 15:00 ` Grant Edwards
2015-10-06 7:51 Richard Rauch
2015-10-06 12:59 ` Mikhail Matusov
2015-10-12 23:57 ` Jonathan Larmour
2015-10-13 12:31 ` David Fernandez
2015-10-14 0:57 ` Frank Pagliughi
2015-10-13 17:20 ` Grant Edwards
2015-10-13 19:38 ` Alex Schuilenburg
2015-10-14 23:05 ` Sergei Gavrikov
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=560F8EB4.4030304@dallaway.org.uk \
--to=john@dallaway.org.uk \
--cc=ecos-discuss@sourceware.org \
--cc=just_abhi22@yahoo.co.in \
/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).