From: Gary Thomas <gary@mlbassoc.com>
To: John Cheetham <john.cheetham@york.com>
Cc: eCos Maintainers <ecos-maintainers@sources.redhat.com>
Subject: Re: eCos port to MCF5272
Date: Wed, 30 Jul 2003 18:41:00 -0000 [thread overview]
Message-ID: <1059590475.10050.2115.camel@hermes> (raw)
In-Reply-To: <MIEFIBINGMBOFEACLDKNOEBCCAAA.john.cheetham@york.com>
On Wed, 2003-07-30 at 12:33, John Cheetham wrote:
> The status, on the sources.redhat.com web page, for the
> MCF5272 platform is "Alpha quality only at this time" and
> "The support for this platform was contributed ... contributed
> ports may not have been tested.".
>
> Is this the current status for this platform?
AFAICT this port has not been touched since May of 2002. I'm
pretty sure that it is still in the same state as when I checked
in in more than a year ago, i.e. still untested directly by any
of the eCos team.
--
Gary Thomas <gary@mlbassoc.com>
MLB Associates
next prev parent reply other threads:[~2003-07-30 18:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-30 18:35 John Cheetham
2003-07-30 18:41 ` Gary Thomas [this message]
2003-07-30 21:03 ` Jonathan Larmour
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=1059590475.10050.2115.camel@hermes \
--to=gary@mlbassoc.com \
--cc=ecos-maintainers@sources.redhat.com \
--cc=john.cheetham@york.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).