From: Yao Qi <qiyaoltc@gmail.com>
To: Simon Marchi <simon.marchi@polymtl.ca>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH 0/4] C++ify varobj a little bit
Date: Tue, 21 Nov 2017 21:36:00 -0000 [thread overview]
Message-ID: <20171121213631.dgdswpfud3fegput@localhost> (raw)
In-Reply-To: <20171118214606.24468-1-simon.marchi@polymtl.ca>
On 17-11-18 16:46:02, Simon Marchi wrote:
> This patch series does a basic C++ification of the varobj code, enough
> to get rid of the VECs. It looks regression free according to the
> buildbot.
I go through them quickly, and they look good to me.
--
Yao
next prev parent reply other threads:[~2017-11-21 21:36 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-18 21:46 Simon Marchi
2017-11-18 21:46 ` [PATCH 2/4] Make varobj::children an std::vector Simon Marchi
2017-11-18 21:46 ` [PATCH 4/4] Remove DEF_VEC_P (varobj_p) Simon Marchi
2017-11-18 21:46 ` [PATCH 3/4] Replace VEC (varobj_update_result) with std::vector Simon Marchi
2017-11-18 21:57 ` [PATCH 1/4] Basic c++ification of varobj Simon Marchi
2017-11-21 21:31 ` Yao Qi
2017-11-22 20:04 ` Simon Marchi
2017-11-22 10:44 ` Pedro Alves
2017-11-22 20:05 ` Simon Marchi
2017-11-21 21:36 ` Yao Qi [this message]
2017-11-22 20:10 ` [PATCH 0/4] C++ify varobj a little bit Simon Marchi
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=20171121213631.dgdswpfud3fegput@localhost \
--to=qiyaoltc@gmail.com \
--cc=gdb-patches@sourceware.org \
--cc=simon.marchi@polymtl.ca \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).