Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Pedro Alves <palves@redhat.com>
To: Paul.Koning@dell.com
Cc: sergiodj@redhat.com, gdb-patches@sourceware.org
Subject: Re: [PATCH] fix build failure with Python 3.7
Date: Fri, 08 Jun 2018 14:55:00 -0000	[thread overview]
Message-ID: <f34f31ff-6721-8ea4-9f58-fe32bab4853a@redhat.com> (raw)
In-Reply-To: <7EBB2FFE-48D7-4361-ACA8-A9CB87031CA6@dell.com>

On 06/08/2018 03:37 PM, Paul.Koning@dell.com wrote:

>> Thanks.  AFAICT, everything's sorted out.  Anything holding this back?
> 
> Just waiting for approval to commit.
> 

Ah, but you already have it:

 https://sourceware.org/ml/gdb-patches/2018-06/msg00015.html

Sorry if that wasn't clear.

Thanks,
Pedro Alves


  reply	other threads:[~2018-06-08 14:55 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <96198491-96D8-42F0-9956-1C2BC9277050@dell.com>
2018-05-31 20:45 ` Sergio Durigan Junior
2018-05-31 21:25   ` Paul.Koning
2018-06-01  1:27     ` Tom Tromey
2018-06-01 11:58       ` Phil Muldoon
     [not found]     ` <87d0xb34jw.fsf@redhat.com>
2018-06-01 11:56       ` Phil Muldoon
2018-06-01 12:16     ` Pedro Alves
2018-06-01 12:54       ` Paul.Koning
2018-06-01 13:10         ` Pedro Alves
2018-06-01 13:22           ` Paul.Koning
2018-06-01 13:36             ` Pedro Alves
2018-06-01 13:37               ` Pedro Alves
2018-06-01 13:47                 ` Paul.Koning
     [not found]                   ` <b1db3ded-7053-3d2b-773e-31ecd20efd90@redhat.com>
2018-06-08 14:37                     ` Paul.Koning
2018-06-08 14:55                       ` Pedro Alves [this message]
2018-06-08 17:36                         ` Paul.Koning
2018-06-09  0:26                           ` 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=f34f31ff-6721-8ea4-9f58-fe32bab4853a@redhat.com \
    --to=palves@redhat.com \
    --cc=Paul.Koning@dell.com \
    --cc=gdb-patches@sourceware.org \
    --cc=sergiodj@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