From: Wu Zhou <woodzltc@cn.ibm.com>
To: Daniel Jacobowitz <drow@false.org>
Cc: gdb-patches@sources.redhat.com, eliz@gnu.org
Subject: Re: [RFC/Patch] replace sprintf calls in remote.c with xsnprintf
Date: Fri, 17 Jun 2005 04:38:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.63.0506171212050.10583@localhost.localdomain> (raw)
In-Reply-To: <20050617015950.GD17013@nevyn.them.org>
On Thu, 16 Jun 2005, Daniel Jacobowitz wrote:
> Sorry - not sure how this slipped through the cracks.
No problem.
>
> On Sun, May 29, 2005 at 07:07:45AM -0700, Wu Zhou wrote:
> > Below is the revised patch. Please review and comment. TIA.
> >
> > <2005-05-29> Wu Zhou <woodzltc@cn.ibm.com>
> >
> > * remote.c (set_thread, remote_thread_alive): Replace sprintf
> > call with xsnprintf.
> > (remote_threads_extra_info, extended_remote_restart)
> > (remote_check_symbols, store_register_using_P)
> > (compare_sections_command): Ditto.
>
> This is OK.
Commited. Thanks.
Cheers
- Wu Zhou
prev parent reply other threads:[~2005-06-17 4:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-26 14:59 Wu Zhou
2005-05-28 18:53 ` Daniel Jacobowitz
2005-05-29 6:55 ` Wu Zhou
2005-06-17 2:00 ` Daniel Jacobowitz
2005-06-17 4:38 ` Wu Zhou [this message]
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=Pine.LNX.4.63.0506171212050.10583@localhost.localdomain \
--to=woodzltc@cn.ibm.com \
--cc=drow@false.org \
--cc=eliz@gnu.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