From: DJ Delorie <dj@redhat.com>
To: drow@false.org
Cc: gdb@sourceware.org
Subject: Re: gdb support for m32c?
Date: Tue, 14 Mar 2006 02:38:00 -0000 [thread overview]
Message-ID: <200603140238.k2E2cO8k018135@greed.delorie.com> (raw)
In-Reply-To: <20060314022350.GA1097@nevyn.them.org> (message from Daniel Jacobowitz on Mon, 13 Mar 2006 21:23:50 -0500)
> If you want maintainership of this sim, I don't think anyone will
> object; could you add yourself to sim/MAINTAINERS?
Done, attached. Thanks!
> It'd be nice to get the GDB port finalized, one way or another.
It's still waiting for Jim's prologue analyzer work:
http://sources.redhat.com/ml/gdb-patches/2006-01/msg00341.html
2006-03-13 DJ Delorie <dj@redhat.com>
* MAINTAINERS: Add self as m32c sim maintainer.
Index: MAINTAINERS
===================================================================
RCS file: /cvs/src/src/sim/MAINTAINERS,v
retrieving revision 1.16
diff -p -U3 -r1.16 MAINTAINERS
--- MAINTAINERS 26 May 2005 21:37:09 -0000 1.16
+++ MAINTAINERS 14 Mar 2006 02:35:53 -0000
@@ -15,6 +15,7 @@ igen (igen simulators)
ppc Andrew Cagney <ac131313@redhat.com>
m68hc11 Stephane Carrez <stcarrez@nerim.fr>
sh (global maintainers)
+m32c DJ Delorie <dj@redhat.com>
common Ben Elliston <bje@gnu.org>
common Frank Ch. Eigler <fche@redhat.com>
* (target, then global maintainers)
next prev parent reply other threads:[~2006-03-14 2:38 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-10 21:30 DJ Delorie
2006-03-10 22:45 ` Hans-Wolfgang Loidl
2006-03-10 22:55 ` DJ Delorie
2006-03-10 23:12 ` Hans-Wolfgang Loidl
2006-03-10 23:21 ` DJ Delorie
2006-03-14 2:23 ` Daniel Jacobowitz
2006-03-14 2:38 ` DJ Delorie [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-03-08 22:11 Hans-Wolfgang Loidl
2006-03-09 3:24 ` Daniel Jacobowitz
2006-03-09 14:41 ` Hans-Wolfgang Loidl
2006-03-09 15:00 ` Daniel Jacobowitz
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=200603140238.k2E2cO8k018135@greed.delorie.com \
--to=dj@redhat.com \
--cc=drow@false.org \
--cc=gdb@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).