From: Tom Tromey <tromey@redhat.com>
To: Yao Qi <yao@codesourcery.com>
Cc: <gdb-patches@sourceware.org>
Subject: Re: [PATCH 2/5] Move vec to common/
Date: Fri, 13 Apr 2012 17:30:00 -0000 [thread overview]
Message-ID: <87aa2fy1yj.fsf@fleche.redhat.com> (raw)
In-Reply-To: <1331908966-5527-3-git-send-email-yao@codesourcery.com> (Yao Qi's message of "Fri, 16 Mar 2012 22:42:43 +0800")
>>>>> "Yao" == Yao Qi <yao@codesourcery.com> writes:
Yao> ITSET is using vec, so when moving ITSET bits to gdb/common/, it is
Yao> straightforward to move vec.c and vec.h to gdb/common as well.
I don't know if this is still relevant, but this patch is ok if so.
Tom
next prev parent reply other threads:[~2012-04-13 17:30 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-16 14:44 [PATCH 1/5] Define target_core_of_thread in gdbserver Yao Qi
2012-03-16 14:44 ` [PATCH 2/5] Move vec to common/ Yao Qi
2012-04-13 17:30 ` Tom Tromey [this message]
2012-04-19 7:15 ` [committed]: " Yao Qi
2012-03-16 14:47 ` [PATCH 1/5] Define target_core_of_thread in gdbserver Yao Qi
2012-04-13 17:35 ` Tom Tromey
2012-04-19 6:03 ` [committed]: " Yao Qi
2012-03-16 15:01 [PATCH 0/5] Preparatory patches for ITSET in GDBserver Yao Qi
2012-03-16 15:02 ` [PATCH 2/5] Move vec to common/ Yao Qi
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=87aa2fy1yj.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=yao@codesourcery.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