From: Tom Tromey <tromey@redhat.com>
To: gdb-patches@sourceware.org
Subject: [RFC v2 0/9] move more code into common/
Date: Thu, 06 Feb 2014 19:29:00 -0000 [thread overview]
Message-ID: <1391714966-12125-1-git-send-email-tromey@redhat.com> (raw)
This is a refresh of an earlier series to share more code between gdb
and gdbserver.
The original series is here:
https://sourceware.org/ml/gdb-patches/2014-01/msg00747.html
Changes since version 1:
* Renamed new files to print-utils.[ch] (patch #1)
* Updated some comments in response to Yao's review (patch #2)
* Added missing _() markers (patch #2)
* Realized that I didn't remove newly shared declarations in patch #2;
deleted them.
All other patches are, I believe, unchanged and approved by Pedro.
Tom
next reply other threads:[~2014-02-06 19:29 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-06 19:29 Tom Tromey [this message]
2014-02-06 19:29 ` [RFC v2 1/9] share "cell" code Tom Tromey
2014-02-06 19:29 ` [RFC v2 3/9] don't let bin2hex call strlen Tom Tromey
2014-02-06 19:29 ` [RFC v2 4/9] don't let hexify " Tom Tromey
2014-02-06 19:29 ` [RFC v2 2/9] move some rsp bits into rsp-low.h Tom Tromey
2014-02-13 9:02 ` Yao Qi
2014-02-13 10:38 ` Pedro Alves
2014-02-14 2:00 ` Yao Qi
2014-02-13 15:08 ` Tom Tromey
2014-02-14 1:36 ` Yao Qi
2014-02-06 19:38 ` [RFC v2 5/9] replace hexify with bin2hex Tom Tromey
2014-02-06 19:41 ` [RFC v2 6/9] replace convert_int_to_ascii " Tom Tromey
2014-02-06 20:23 ` [RFC v2 7/9] replace unhexify with hex2bin Tom Tromey
2014-02-06 20:23 ` [RFC v2 8/9] replace convert_ascii_to_int " Tom Tromey
2014-02-06 20:24 ` [RFC v2 9/9] update rsp-low comments Tom Tromey
2014-02-07 12:53 ` [RFC v2 0/9] move more code into common/ Pedro Alves
2014-02-12 16:57 ` Tom Tromey
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=1391714966-12125-1-git-send-email-tromey@redhat.com \
--to=tromey@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