From: John Dallaway <john@dallaway.org.uk>
To: ecos-maintainers@ecos.sourceware.org
Cc: Ross Younger <wry@ecoscentric.com>,
Simon Kallweit <simon.kallweit@intefo.ch>,
Sergei Gavrikov <sergei.gavrikov@gmail.com>,
Melanie Rieback <melanie@cs.vu.nl>,
Paul Beskeen <paulb@ecoscentric.com>,
Rutger Hofman <rutger@cs.vu.nl>
Subject: Re: NAND & YAFFS
Date: Fri, 15 May 2009 09:48:00 -0000 [thread overview]
Message-ID: <4A0D3A59.7070105@dallaway.org.uk> (raw)
In-Reply-To: <4A0C6674.5030006@cs.vu.nl>
Rutger Hofman wrote:
> Another reason that I think eCosPro has not chosen the wisest course
> here is the shadow it throws into the future. Isn't it an unattractive
> proposition for anyone who would want to contribute that they will only
> afterwards be informed that their work may be out-competed by eCosPro
> themselves?
I have already responded to Rutger privately and am sure eCosCentric
will respond in due course. In the meantime, I would like to remind
everyone that the eCos maintainers operate independently of any
commercial organisation they may be a affiliated to. They try to ensure
the best possible outcome for the eCos project at two levels:
a) Technical progress
b) Health and growth of the user community
Be assured that all contributions are evaluated on their own technical
merits and that the views of the community will be taken into account.
John Dallaway
eCos maintainer
next prev parent reply other threads:[~2009-05-15 9:48 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 [this message]
2009-05-15 9:52 ` Andrew Lunn
2009-05-15 10:18 ` Simon Kallweit
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=4A0D3A59.7070105@dallaway.org.uk \
--to=john@dallaway.org.uk \
--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=simon.kallweit@intefo.ch \
--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).