public inbox for ecos-maintainers@sourceware.org
 help / color / mirror / Atom feed
From: Gary Thomas <gary@mlbassoc.com>
To: epiria@fastwebnet.it
Cc: eCos Maintainers <ecos-maintainers@ecos.sourceware.org>
Subject: Re: eCos port to ColdFire
Date: Wed, 14 Dec 2005 15:10:00 -0000	[thread overview]
Message-ID: <1134573002.14186.55.camel@hermes> (raw)
In-Reply-To: <4381C3B700026806@ms005msg.mail.fw>

On Wed, 2005-12-14 at 15:03 +0000, epiria@fastwebnet.it wrote:
> Dear eCos maintainers,
> 
> on November 18 2005 I posted to the ecos-patches mailing list a
> thorough rewrite of the eCos port to the ColdFire architecture.
> This required me months of hard work, but I wanted to fix the ColdFire
> port available in the current eCos distribution, which is widely known to
> be broken.
> I sent you also the copyright assignment that now you should have received.
> I know that you reserve the right to refuse any source code additions.
> What really disconcerts me is that I didn't receive the minimum
> feedback from you, neither on the eCos mailing lists nor in private email,
> about what I think is a major improvement to the operating system.
> Has this to do with the fact that eCosCentric also sells a port of eCos to
> the ColdFire?
> I'm looking forward to receive an answer from you.

Mr. Piria,

I'm not speaking for the eCos maintainers as a whole, but I bid you
patience.  These things take time.  In my own case, I've been out of
my office (on other business) since your submission and I've not had
any time at all to review your efforts.

-- 
------------------------------------------------------------
Gary Thomas                 |  Consulting for the
MLB Associates              |    Embedded world
------------------------------------------------------------

  reply	other threads:[~2005-12-14 15:10 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-12-14 15:03 epiria
2005-12-14 15:10 ` Gary Thomas [this message]
2005-12-15 15:18 ` Andrew Lunn

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=1134573002.14186.55.camel@hermes \
    --to=gary@mlbassoc.com \
    --cc=ecos-maintainers@ecos.sourceware.org \
    --cc=epiria@fastwebnet.it \
    /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).