From: Andrew Burgess <aburgess@redhat.com>
To: Joel Brobecker <brobecker@adacore.com>
Cc: gdb-patches@sourceware.org
Subject: Re: GDB 12 preparation and target date?
Date: Wed, 2 Feb 2022 17:00:55 +0000 [thread overview]
Message-ID: <20220202170055.GJ425591@redhat.com> (raw)
In-Reply-To: <Ye01Pk+wvX77Hf0V@adacore.com>
* Joel Brobecker via Gdb-patches <gdb-patches@sourceware.org> [2022-01-23 15:00:14 +0400]:
> Let me know what you guys think, and also please let us know what
> patches you think should be included in GDB 12, and why they are
> important.
I'd like to see the MI commands in Python patch land:
https://sourceware.org/pipermail/gdb-patches/2022-January/185332.html
this is an alternative to the series Jan posted, but I believe that
Jan and I are both happy with my version, linked above.
Thanks,
Andrew
next prev parent reply other threads:[~2022-02-02 17:01 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 [this message]
2022-02-02 19:31 ` John Baldwin
2022-02-13 14:33 ` Joel Brobecker
2022-02-14 18:51 ` John Baldwin
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=20220202170055.GJ425591@redhat.com \
--to=aburgess@redhat.com \
--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).