From: Daniel Jacobowitz <drow@false.org>
To: gdb-patches@sources.redhat.com
Subject: Re: RFA: contribute Renesas M32C sim
Date: Mon, 23 Jan 2006 02:03:00 -0000 [thread overview]
Message-ID: <20060123020349.GM27224@nevyn.them.org> (raw)
In-Reply-To: <vt2br1us7uh.fsf@theseus.home.>
On Wed, Oct 12, 2005 at 03:12:22PM -0700, Jim Blandy wrote:
>
> I think the attached patch should address the points you raised:
>
> - I added copyright notices.
> - I ran the code through gdb_indent.sh, and fixed up some further messes.
> - I added a comment to m32c.opc:prefix.
Hi Jim,
Anything ever come of this? I don't see a reason to hold off on the
revised patch.
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2006-01-23 2:03 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-07 20:46 Jim Blandy
2005-10-07 21:03 ` Daniel Jacobowitz
2005-10-09 0:29 ` Jim Blandy
2005-10-09 20:15 ` Daniel Jacobowitz
2005-10-12 18:21 ` Jim Blandy
[not found] ` <jimb@redhat.com>
2005-12-14 18:40 ` DJ Delorie
2005-12-15 0:01 ` Daniel Jacobowitz
2005-12-15 14:48 ` Jim Blandy
2005-12-15 16:18 ` Daniel Jacobowitz
2005-10-12 22:12 ` Jim Blandy
2006-01-23 2:03 ` Daniel Jacobowitz [this message]
2006-01-23 22:11 ` Jim Blandy
2005-10-15 12:06 ` Eli Zaretskii
2005-10-17 23:26 ` Jim Blandy
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=20060123020349.GM27224@nevyn.them.org \
--to=drow@false.org \
--cc=gdb-patches@sources.redhat.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