public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: John Baldwin <jhb@FreeBSD.org>
To: Joel Brobecker <brobecker@adacore.com>
Cc: gdb-patches@sourceware.org
Subject: Re: GDB 12 preparation and target date?
Date: Mon, 14 Feb 2022 10:51:04 -0800	[thread overview]
Message-ID: <7981a7f9-a98d-bcab-9478-473b9927c2c1@FreeBSD.org> (raw)
In-Reply-To: <YgkWp2LEFPoeCaJR@adacore.com>

On 2/13/22 6:33 AM, Joel Brobecker wrote:
> Hi John,
> 
>> I'd like to land my FreeBSD async mode series in GDB 12.
>>
>> https://sourceware.org/pipermail/gdb-patches/2022-January/185345.html
> 
> I m now keeping an eye on this patch series. Just make sure I understand
> the situation well: As far as I can tell, the patch series has been
> reviewed by Tom (Jan 14th), and the ball is now in your court to send
> a new patch series?

Tom had generally signed off on v4, but he noted some questions he wasn't
sure about.  Those questions were valid and uncovered some other bugs
which I posted as v5 (the link above is the cover letter for v5).  Eli
has approved the NEWS blurb in v5.  I think the only outstanding bits
are if patches 4 and 7 in the v5 series are ok?

-- 
John Baldwin

      reply	other threads:[~2022-02-14 18:51 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-23 11:00 Joel Brobecker
2022-01-26 15:07 ` Tom Tromey
2022-01-27  3:54   ` Joel Brobecker
2022-01-28  3:03     ` Tiezhu Yang
2022-01-28  9:40 ` Aktemur, Tankut Baris
2022-02-02 17:00 ` Andrew Burgess
2022-02-02 19:31 ` John Baldwin
2022-02-13 14:33   ` Joel Brobecker
2022-02-14 18:51     ` John Baldwin [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=7981a7f9-a98d-bcab-9478-473b9927c2c1@FreeBSD.org \
    --to=jhb@freebsd.org \
    --cc=brobecker@adacore.com \
    --cc=gdb-patches@sourceware.org \
    /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).