From: Simon Kallweit <simon.kallweit@intefo.ch>
To: Andrew Lunn <andrew.lunn@ascom.ch>
Cc: Rutger Hofman <rutger@cs.vu.nl>,
Ross Younger <wry@ecoscentric.com>,
ecos-maintainers@ecos.sourceware.org,
Sergei Gavrikov <sergei.gavrikov@gmail.com>,
Melanie Rieback <melanie@cs.vu.nl>,
Paul Beskeen <paulb@ecoscentric.com>
Subject: Re: NAND & YAFFS
Date: Fri, 15 May 2009 10:18:00 -0000 [thread overview]
Message-ID: <4A0D4189.6040109@intefo.ch> (raw)
In-Reply-To: <20090515095150.GH17679@ma.tech.ascom.ch>
Andrew Lunn wrote:
> Hi Folks
>
> This is also not the first time this has happened. A recent example
> would be the Cortex-M3 work. If i dug into the email archives i could
> find other examples. There is a possibility of it happening again soon
> as well. eCosCentric have a more modern lwIP port in there tree than
> the current in anoncvs. I understand they have optimized it for small
> platform and made it more stable. There is the current effort going on
> to update the anoncvs lwip code. When this reaches maturity, which
> looks like will happen soon, are eCosCentric going to pull out there
> trump card again and contribute there lwip port?
Well well, I almost saw that coming :/
I just wanted to say that I fully agree with your views Andrew. I really
hope the situation can be improved in the future. I think all parties
could win by collaborating more with each other. Most of what can be
improved here unfortunately seems to be in the hands of eCosCentric.
They are the main force behind eCos development, invest lots of man-time
into the project and therefore have quite a bit of authority over
development. Unless the community wants to fork the project and go their
own way, communication between eCosCentric and the community needs to be
improved. Or at least we need a clear statement from eCosCentric towards
what the community can and cannot expect.
Simon
next prev parent reply other threads:[~2009-05-15 10:18 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-13 13:59 Ross Younger
2009-05-13 14:22 ` Simon Kallweit
2009-05-13 16:28 ` Sergei Gavrikov
2009-05-13 19:03 ` John Dallaway
2009-05-15 16:50 ` Ross Younger
2009-05-16 10:43 ` Andrew Lunn
2009-05-16 12:50 ` Ross Younger
2009-05-18 7:13 ` Andrew Lunn
2009-05-18 10:42 ` Rutger Hofman
2009-06-02 18:18 ` John Dallaway
2009-06-03 6:55 ` Andrew Lunn
2009-05-14 18:41 ` Rutger Hofman
2009-05-15 9:48 ` John Dallaway
2009-05-15 9:52 ` Andrew Lunn
2009-05-15 10:18 ` Simon Kallweit [this message]
2009-05-16 9:50 ` Andrew Lunn
2009-05-18 9:39 ` Paul Beskeen
2009-05-18 9:55 ` Simon Kallweit
2009-05-15 16:19 ` Paul Beskeen
2009-05-15 6:44 cetoni GmbH - Uwe Kindler
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=4A0D4189.6040109@intefo.ch \
--to=simon.kallweit@intefo.ch \
--cc=andrew.lunn@ascom.ch \
--cc=ecos-maintainers@ecos.sourceware.org \
--cc=melanie@cs.vu.nl \
--cc=paulb@ecoscentric.com \
--cc=rutger@cs.vu.nl \
--cc=sergei.gavrikov@gmail.com \
--cc=wry@ecoscentric.com \
/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).