From: John Dallaway <john@dallaway.org.uk>
To: Liam Knight <liam.knight01@gmail.com>
Cc: eCos Discussion <ecos-discuss@sourceware.org>
Subject: [ECOS] Re: Is eCosPro a fork of eCos?
Date: Thu, 28 Mar 2013 16:25:00 -0000 [thread overview]
Message-ID: <51546EFC.5050603@dallaway.org.uk> (raw)
In-Reply-To: <CA+QuBBfU01exmSPQQuXqhGOLASYa=4w32Gp=R0bR9DaUWvJJtA@mail.gmail.com>
Liam
On 28/03/13 14:40, Liam Knight wrote:
> Apologies for the wide distribution. Unfortunately the owner of the
> eCos group on the social media website I belong to does not believe in
> free speech and has censured my responses to the group. It appears
> that if you express an opinion that differs to his, he would classify
> it as off topic or abusive, as so moderate and censure it. Fortunately
> we live in a world of free speech so I would appreciate that members
> of this particular group on this list point the group to this email
> which shoould get archived somewhere here:
> http://ecos.sourceware.org/ml/ecos-discuss/2013-03/
You obviously feel very strongly about this. The discussion on LinkedIn
was veering off-topic and so I offered to call you and discuss. Many of
the things you are accusing me of are not correct. The LinkedIn forum is
indeed moderated. This is the first time I have ever considered it
appropriate to moderate a discussion.
For the record:
> John started a discussion topic about eCosCentric and whether eCosPro
> is a fork of eCos
In fact, I have responded to a direct question from you. I have not
mentioned forking at all!
> you appear to be saying you have excluded members of eCosCentric from
> membership of the group because eCosCentric have forked eCos
No, I am not saying that at all.
> Also, you infer from your last response to me on the group
> that you have spoken to eCosCentric and that they confirm your
> position that eCosPro is a fork is correct.
Liam, I cannot see how you can possibly infer that. I know for a fact,
that eCosCentric does not consider eCosPro to be a fork.
If you want to discuss whether eCosPro is a fork of eCos or not in a
public forum, go right ahead. But please don't put words into my mouth.
If you want to discuss why I think it is good to provide a networking
forum for professional users of the free and open source eCos RTOS,
let's arrange to talk.
John Dallaway
--
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:[~2013-03-28 16:25 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-28 14:40 [ECOS] " Liam Knight
2013-03-28 16:25 ` John Dallaway [this message]
2013-03-28 18:40 ` [ECOS] " Liam Knight
2013-03-31 8:08 ` [ECOS] why should ISR arrange that the same interrupt would not recur until DSR completed? Randy
2013-03-31 12:06 ` Stanislav Meduna
2013-03-31 14:48 ` Randy
2013-04-01 11:59 ` Stanislav Meduna
2013-04-07 12:05 ` Randy
2013-04-07 13:21 ` Stanislav Meduna
2013-04-10 8:36 ` [ECOS] put unmask in ISR rather than DSR causing interrupt lost Randy
2013-04-10 9:27 ` 回复: " Randy
2013-04-14 11:39 ` 回复: " Randy
2013-04-18 2:50 ` [ECOS] why did not enable interrupt before call pending dsr while not use interrupt stack Randy
2013-03-31 22:33 [ECOS] Re: Is eCosPro a fork of eCos? Ken Yee
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=51546EFC.5050603@dallaway.org.uk \
--to=john@dallaway.org.uk \
--cc=ecos-discuss@sourceware.org \
--cc=liam.knight01@gmail.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).