From: Joel Brobecker <brobecker@adacore.com>
To: gdb-patches@sourceware.org
Cc: Joel Brobecker <brobecker@adacore.com>, aburgess@redhat.com
Subject: GDB 12 branching next weekend (2022-03-20 or 2022-03-21)?
Date: Sun, 13 Mar 2022 08:55:43 +0400 [thread overview]
Message-ID: <Yi15T3HiZjGlLbWq@adacore.com> (raw)
Hi everyone,
Given the advancement on the two remaining items identified for
the GDB 12 release, I think we can shoot for branching this coming
weekend:
Sat/Sun March 20-21.
If you guys see some issues with that, then please let us know.
Otherwise, let's go for it!
Cheers everyone.
---
Fixed Since the Previous Update:
--------------------------------
<none>
Added Since the Last Update:
----------------------------
<none>
Other Ongoing Items:
--------------------
* TBC: [BarisA/AndrewB] <PR cli/28833>
Ctrl-D distorts GDB prompt
https://sourceware.org/bugzilla/show_bug.cgi?id=28833
Baris requested that we consider the bug above, which seems
to be a GDB 11 regression for Baris.
IIUC, Andrew fixed the issue in upstream's readline, and
now we just need to backport it.
https://lists.gnu.org/archive/html/bug-readline/2022-03/msg00005.html
Backport request on GDB ml:
https://sourceware.org/pipermail/gdb-patches/2022-March/186391.html
There was a suggestion that we use a more limited bug safer
approach for GDB 12. I did not look at the patch, but if it
helps make people more comfortable, this seems like a valid
approach.
* [AndrewB] create GDB/MI commands using python
Explicit request to include in GDB 12; accepted as the patches
were sent prior to the start of the GDB 12 release process.
Latest version (v5) pasted by Andrew, and approved by Tom:
https://sourceware.org/pipermail/gdb-patches/2022-February/186176.html
Let's push the patch ;-).
Reminder: Tentative Schedule:
-----------------------------
- GDB 12 branching: ~Mar 20-25;
- GDB 12.1 release 2 weeks later, so early Apr.
--
Joel
next reply other threads:[~2022-03-13 4:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-13 4:55 Joel Brobecker [this message]
2022-03-16 20:47 ` Andrew Burgess
2022-03-18 3:33 ` Joel Brobecker
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=Yi15T3HiZjGlLbWq@adacore.com \
--to=brobecker@adacore.com \
--cc=aburgess@redhat.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).