public inbox for ecos-bugs@sourceware.org
help / color / mirror / Atom feed
From: bugzilla-daemon@bugs.ecos.sourceware.org
To: backlog@bugs.ecos.sourceware.org
Subject: [Bug 1000761] eCos support for MPC5xxx MCUs
Date: Tue, 14 Sep 2010 15:39:00 -0000	[thread overview]
Message-ID: <20100914153903.AC17E2F78010@mail.ecoscentric.com> (raw)
In-Reply-To: <bug-1000761-776@http.bugs.ecos.sourceware.org/>

Please do not reply to this email. Use the web interface provided at:
http://bugs.ecos.sourceware.org/show_bug.cgi?id=1000761

Dave Peterson <dpeter@woodward.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |dpeter@woodward.com

--- Comment #27 from Dave Peterson <dpeter@woodward.com> 2010-09-14 16:38:59 BST ---
How do I find out the status of the MPC55xx support for eCos?
I have been waiting for this to be added to the release, but I don't know how
to find out the timeframe.

-- 
Configure bugmail: http://bugs.ecos.sourceware.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.


       reply	other threads:[~2010-09-14 15:39 UTC|newest]

Thread overview: 67+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-1000761-776@http.bugs.ecos.sourceware.org/>
2010-09-14 15:39 ` bugzilla-daemon [this message]
2010-09-26 12:02 ` bugzilla-daemon
2010-09-28 17:14 ` bugzilla-daemon
2012-05-30 13:52 ` bugzilla-daemon
2012-05-31 12:55 ` bugzilla-daemon
     [not found] <bug-1000761-13@http.bugs.ecos.sourceware.org/>
2009-05-12 16:28 ` bugzilla-daemon
2009-05-12 22:11 ` bugzilla-daemon
2009-05-14  8:17 ` bugzilla-daemon
2009-05-21 12:31 ` bugzilla-daemon
2009-05-21 14:25 ` bugzilla-daemon
2009-05-22 12:29 ` bugzilla-daemon
2009-06-02  9:55 ` bugzilla-daemon
2009-06-08 19:10 ` bugzilla-daemon
2009-07-06 20:52 ` bugzilla-daemon
2009-07-07  6:47 ` bugzilla-daemon
2009-07-20 20:17 ` bugzilla-daemon
2009-07-20 20:47 ` bugzilla-daemon
2009-07-22 14:13 ` bugzilla-daemon
2010-09-14 15:39 ` bugzilla-daemon
2010-09-26 12:02 ` bugzilla-daemon
2010-09-28 17:14 ` bugzilla-daemon
2012-05-30 13:52 ` bugzilla-daemon
2012-05-31 12:55 ` bugzilla-daemon
2012-05-31 13:54 ` bugzilla-daemon
2012-05-31 13:55 ` bugzilla-daemon
2012-05-31 13:56 ` bugzilla-daemon
2012-06-04  9:53 ` bugzilla-daemon
2012-06-04 19:15 ` bugzilla-daemon
2012-06-05  7:57 ` bugzilla-daemon
2012-07-05  9:40 ` bugzilla-daemon
2012-07-05  9:41 ` bugzilla-daemon
2012-07-08 16:02 ` bugzilla-daemon
2012-07-08 17:27 ` bugzilla-daemon
2012-08-01 16:36 ` bugzilla-daemon
2012-08-01 16:37 ` bugzilla-daemon
2012-08-01 16:38 ` bugzilla-daemon
2012-08-01 16:39 ` bugzilla-daemon
2012-08-06  8:49 ` bugzilla-daemon
2012-08-06  8:55 ` bugzilla-daemon
2012-08-06  9:01 ` bugzilla-daemon
2012-08-06  9:37 ` bugzilla-daemon
2012-08-06 15:30 ` bugzilla-daemon
2012-08-06 15:31 ` bugzilla-daemon
2012-08-06 15:33 ` bugzilla-daemon
2012-08-06 15:42 ` bugzilla-daemon
2012-08-08  7:52 ` bugzilla-daemon
2012-08-13  7:18 ` bugzilla-daemon
2012-08-13 21:12 ` bugzilla-daemon
2012-09-30 15:38 ` bugzilla-daemon
2012-09-30 15:41 ` bugzilla-daemon
2012-09-30 19:17 ` bugzilla-daemon
2012-10-01  9:58 ` bugzilla-daemon
2012-10-05 13:06 ` bugzilla-daemon
2012-10-14 15:23 ` bugzilla-daemon
2012-10-29  9:50 ` bugzilla-daemon
2012-10-29 10:05 ` bugzilla-daemon
2012-10-29 16:58 ` bugzilla-daemon
2012-10-29 18:09 ` bugzilla-daemon
2012-10-30 13:26 ` bugzilla-daemon
2013-02-04 16:59 ` bugzilla-daemon
2013-02-04 17:01 ` bugzilla-daemon
2009-05-11 17:06 [Bug 1000761] New: " bugzilla-daemon
2009-06-02  9:56 ` [Bug 1000761] " bugzilla-daemon
2009-08-06 14:30 ` bugzilla-daemon
2009-08-06 18:44 ` bugzilla-daemon
2009-08-06 18:49 ` bugzilla-daemon
2009-08-21 13:57 ` bugzilla-daemon
2009-08-21 14:04 ` bugzilla-daemon

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=20100914153903.AC17E2F78010@mail.ecoscentric.com \
    --to=bugzilla-daemon@bugs.ecos.sourceware.org \
    --cc=backlog@bugs.ecos.sourceware.org \
    /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).