From: Kevin Buettner <kevinb@redhat.com>
To: gdb-patches@sourceware.org
Subject: Re: [rx-sim]: add cycle accuracy
Date: Wed, 28 Jul 2010 05:15:00 -0000 [thread overview]
Message-ID: <20100727221503.59032690@mesquite.lan> (raw)
In-Reply-To: <201007280206.o6S26g5e013725@greed.delorie.com>
On Tue, 27 Jul 2010 22:06:42 -0400
DJ Delorie <dj@redhat.com> wrote:
> There doesn't seem to be an rx-specific sim maintainer. Since I wrote
> it, should I be the maintainer?
Yes, I think you should be the maintainer for the rx sim.
Kevin
next prev parent reply other threads:[~2010-07-28 5:15 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-28 2:07 DJ Delorie
2010-07-28 2:08 ` DJ Delorie
2010-07-28 5:15 ` Kevin Buettner [this message]
2010-07-28 20:02 ` Maintainers [was Re: [rx-sim]: add cycle accuracy] DJ Delorie
2010-07-28 20:04 ` Michael Snyder
2010-07-28 21:56 ` DJ Delorie
2010-07-28 22:27 ` Andreas Schwab
2010-07-28 22:31 ` DJ Delorie
2010-07-28 15:44 ` [rx-sim]: add cycle accuracy Tom Tromey
2010-07-28 21:59 ` DJ Delorie
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=20100727221503.59032690@mesquite.lan \
--to=kevinb@redhat.com \
--cc=gdb-patches@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).