From: Pedro Alves <palves@redhat.com>
To: Simon Marchi <simon.marchi@ericsson.com>, gdb-patches@sourceware.org
Subject: Re: [PATCH c++ 0/3] Some C++ patches
Date: Fri, 09 Oct 2015 14:09:00 -0000 [thread overview]
Message-ID: <5617CAA5.6040608@redhat.com> (raw)
In-Reply-To: <1444399099-31226-1-git-send-email-simon.marchi@ericsson.com>
On 10/09/2015 02:58 PM, Simon Marchi wrote:
> Here are some unrelated C++ patches. I don't really see a logical order to
> send the remaining patches, so my strategy is to try to build and send the
> patches that fix the first errors I hit. Rinse & repeat until done.
LGTM.
Thanks,
Pedro Alves
next prev parent reply other threads:[~2015-10-09 14:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-09 13:58 Simon Marchi
2015-10-09 13:58 ` [PATCH c++ 1/3] arm-linux-tdep: Add explicit cast for int to gdb_syscall conversion Simon Marchi
2015-10-09 13:58 ` [PATCH c++ 2/3] cris: Use enum bfd_endian to represent endianness Simon Marchi
2015-10-09 13:58 ` [PATCH c++ 3/3] i386: Fix type of gdbarch_tdep::register_reggroup_p Simon Marchi
2015-10-09 14:09 ` Pedro Alves [this message]
2015-10-09 14:12 ` [PATCH c++ 0/3] Some C++ patches 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=5617CAA5.6040608@redhat.com \
--to=palves@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=simon.marchi@ericsson.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