From: Luis Machado <luis.machado@arm.com>
To: Joel Brobecker <brobecker@adacore.com>, gdb-patches@sourceware.org
Subject: Re: GDB 12 preparation -- 2022-03-06 update
Date: Mon, 7 Mar 2022 08:50:52 +0000 [thread overview]
Message-ID: <17da0830-6d2d-c279-aa53-63014cae80ce@arm.com> (raw)
In-Reply-To: <YiSJsFO+XMiDkUyN@adacore.com>
On 3/6/22 10:15, Joel Brobecker via Gdb-patches wrote:
> Hi everyone,
>
> We are making very good progress, it seems, on the two issues
> we have identified for GDB 12, so if things continue this way,
> we might be on track to create our first pre-release around
> the time we were targetting, which is March 20-25 (repeated
> at the end of every message, just for the record)!
>
> There has also been ...
>
> https://sourceware.org/bugzilla/show_bug.cgi?id=28616
>
> ... where I wasn't sure why it was marked GDB 12, and have been
> trying to reach out to the person who created the PR. I've tried
> a different email which I think will work. Given that I'm not
> seeing progress on this PR either, I'm hoping this one isn't
> going to be deemed critical (it does seem to happen in unusual
> circumstances, but workarounds once hist are unclear at the moment).
I think this would be nice to fix it for GDB 12 (it is potentially a
small fix), but not critical enough to stop a release. It's been there
for a while after all.
Feel free to drop it from the blockers list. I opened this last year,
but I couldn't finish it due to outstanding circumstances, sorry.
next prev parent reply other threads:[~2022-03-07 8:51 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-06 10:15 Joel Brobecker
2022-03-07 8:50 ` Luis Machado [this message]
2022-03-07 11:45 ` Joel Brobecker
2022-03-07 15:01 ` Tom Tromey
2022-03-07 16:14 ` Joel Brobecker
2022-03-07 17:43 ` Tom Tromey
2022-03-07 15:15 ` Andrew Burgess
2022-03-07 16:14 ` 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=17da0830-6d2d-c279-aa53-63014cae80ce@arm.com \
--to=luis.machado@arm.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).