From: Eli Zaretskii <eliz@elta.co.il>
To: "Kei Sakamoto" <sakamoto.kei@renesas.com>
Cc: ac131313@redhat.com, gdb-patches@sources.redhat.com
Subject: Re: [patch] New m32r remote target, m32rsdi
Date: Wed, 15 Oct 2003 05:51:00 -0000 [thread overview]
Message-ID: <uu16b3v3c.fsf@elta.co.il> (raw)
In-Reply-To: <032401c39228$378ab450$5169910a@KEI> (sakamoto.kei@renesas.com)
> From: "Kei Sakamoto" <sakamoto.kei@renesas.com>
> Date: Tue, 14 Oct 2003 16:53:12 +0900
>
> I attached the revised patch. It is different from the last one as the
> following:
>
> - use serial.[ch] functions instead of socket library
> - documented (doc/gdb.texinfo)
> - add an entry in NEWS
The gdb.texinfo part is okay with me.
next prev parent reply other threads:[~2003-10-15 5:51 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-04 7:57 Kei Sakamoto
2003-08-17 21:03 ` Daniel Jacobowitz
2003-08-21 4:29 ` Kei Sakamoto
2003-09-05 2:59 ` Kei Sakamoto
2003-09-05 14:21 ` Andrew Cagney
2003-09-08 6:13 ` Kei Sakamoto
2003-09-22 7:14 ` Andrew Cagney
2003-10-02 2:26 ` Kei Sakamoto
2003-10-10 1:41 ` Andrew Cagney
2003-10-14 7:53 ` Kei Sakamoto
2003-10-15 5:51 ` Eli Zaretskii [this message]
2003-10-15 14:40 ` Andrew Cagney
2003-10-16 2:43 ` Kei Sakamoto
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=uu16b3v3c.fsf@elta.co.il \
--to=eliz@elta.co.il \
--cc=ac131313@redhat.com \
--cc=gdb-patches@sources.redhat.com \
--cc=sakamoto.kei@renesas.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