Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Sergio Durigan Junior <sergiodj@redhat.com>
To: Tom Tromey <tromey@redhat.com>
Cc: GDB Patches <gdb-patches@sourceware.org>,
	Keith Seitz <keiths@redhat.com>
Subject: Re: [PATCH] Fix for PR c++/15203 and PR c++/15210
Date: Thu, 14 Mar 2013 11:55:00 -0000	[thread overview]
Message-ID: <m38v5qgprs.fsf@redhat.com> (raw)
In-Reply-To: <m3obemgrkl.fsf@redhat.com> (Sergio Durigan Junior's message of	"Thu, 14 Mar 2013 08:15:54 -0300")

On Thursday, March 14 2013, I wrote:

>         http://sourceware.org/ml/gdb-cvs/2013-03/msg00130.html

BTW, it was not clear, is this patch approved for 7.6 branch too?

Thanks,

-- 
Sergio


  reply	other threads:[~2013-03-14 11:55 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-09  5:51 Sergio Durigan Junior
2013-03-13  3:34 ` Sergio Durigan Junior
2013-03-13 20:16 ` Tom Tromey
2013-03-14 11:16   ` Sergio Durigan Junior
2013-03-14 11:55     ` Sergio Durigan Junior [this message]
2013-03-14 14:55       ` Tom Tromey
2013-03-19 14:44         ` Sergio Durigan Junior

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=m38v5qgprs.fsf@redhat.com \
    --to=sergiodj@redhat.com \
    --cc=gdb-patches@sourceware.org \
    --cc=keiths@redhat.com \
    --cc=tromey@redhat.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