Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Pedro Alves <palves@redhat.com>
To: Martin Galvan <martin.galvan@tallertechnologies.com>,
	       gdb-patches@sourceware.org,
	daniel.gutson@tallertechnologies.com
Subject: Re: [PING 2][PATCH][PR gdb/19893] Fix handling of synthetic C++ references
Date: Wed, 18 May 2016 14:54:00 -0000	[thread overview]
Message-ID: <e4c79890-6dd1-2592-4ef8-86618b3cf23a@redhat.com> (raw)
In-Reply-To: <1463582858-11127-1-git-send-email-martin.galvan@tallertechnologies.com>

On 05/18/2016 03:47 PM, Martin Galvan wrote:
> Odd. Just re-generated the patch against master; see if this works.

Works now.  /me looks at patch.

Thanks,
Pedro Alves


  reply	other threads:[~2016-05-18 14:54 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-16 18:28 Martin Galvan
2016-05-18 10:35 ` Pedro Alves
2016-05-18 14:48   ` Martin Galvan
2016-05-18 14:54     ` Pedro Alves [this message]
2016-05-18 15:49     ` Pedro Alves
2016-05-18 16:07       ` Martin Galvan

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=e4c79890-6dd1-2592-4ef8-86618b3cf23a@redhat.com \
    --to=palves@redhat.com \
    --cc=daniel.gutson@tallertechnologies.com \
    --cc=gdb-patches@sourceware.org \
    --cc=martin.galvan@tallertechnologies.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