From: Pedro Alves <palves@redhat.com>
To: Simon Marchi <simon.marchi@polymtl.ca>, gdb-patches@sourceware.org
Subject: Re: [PATCH v2 4/4] Poison XNEW and friends for types that should use new/delete
Date: Fri, 24 Nov 2017 14:26:00 -0000 [thread overview]
Message-ID: <4910fb26-6a04-de45-4989-20fbe5fbd641@redhat.com> (raw)
In-Reply-To: <20171124043416.20706-4-simon.marchi@polymtl.ca>
On 11/24/2017 04:34 AM, Simon Marchi wrote:
> New in v2:
>
> - IsMallocatable -> IsMallocable
> - Formatting
OK.
(I'd suggest removing/simplifying the discussion about SFINAE from
the log. It's just resolved distraction at this point.)
Thanks,
Pedro Alves
next prev parent reply other threads:[~2017-11-24 14:26 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-24 4:34 [PATCH v2 1/4] Create private_inferior class hierarchy Simon Marchi
2017-11-24 4:34 ` [PATCH v2 4/4] Poison XNEW and friends for types that should use new/delete Simon Marchi
2017-11-24 14:26 ` Pedro Alves [this message]
2017-11-24 15:44 ` Simon Marchi
2017-11-24 4:34 ` [PATCH v2 2/4] remote: C++ify thread_item and threads_listing_context Simon Marchi
2017-11-24 14:26 ` Pedro Alves
2017-11-24 4:34 ` [PATCH v2 3/4] Create private_thread_info hierarchy Simon Marchi
2017-11-24 14:26 ` Pedro Alves
2017-11-24 14:26 ` [PATCH v2 1/4] Create private_inferior class hierarchy Pedro Alves
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=4910fb26-6a04-de45-4989-20fbe5fbd641@redhat.com \
--to=palves@redhat.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