public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Pedro Alves <palves@redhat.com>
To: Simon Marchi <simon.marchi@polymtl.ca>, gdb-patches@sourceware.org
Subject: Re: C++ patches
Date: Tue, 21 Jul 2015 10:50:00 -0000	[thread overview]
Message-ID: <55AE23E1.3080606@redhat.com> (raw)
In-Reply-To: <CAFXXi0kOBySak10skPVgJqnD0qw4Y3a2U89N4nc2iq8oCb1x+w@mail.gmail.com>

On 07/19/2015 09:19 PM, Simon Marchi wrote:
> Hi Pedro,
> 
> You mentionned earlier (and on the cxx-conversion wiki page) that
> you'd like people to pick up patches from your C++ branch and
> format/add changelog/post them. I would like to do that, in order to
> make the C++ transition progress.

That'd be fantastic!

> I would naturally start with the
> ptrace refactor patches at the base. However, it seems like that was
> done recently. 

Yeah, I fixed some enum hacks (wrote the "safe enum flags"
patch at the top of the branch) and cleaned up a few other patches,
but the ptrace ones were the only ones that I finished completely
enough to post.

> I want to make sure I don't pull the carpet from
> beneath your feet by posting them. Is it a good time to start doing
> that ?

Absolutely.

IIRC, the only one that I wanted to revisit was the
"VEC don't write 0 to pointer" one -- I don't recall why I needed
that in the first place.

Thanks,
Pedro Alves

      reply	other threads:[~2015-07-21 10:50 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-19 20:20 Simon Marchi
2015-07-21 10:50 ` Pedro Alves [this message]

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=55AE23E1.3080606@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).