From: Joel Brobecker <brobecker@adacore.com>
To: Tom Tromey <tom@tromey.com>
Cc: Joel Brobecker via Gdb-patches <gdb-patches@sourceware.org>,
Joel Brobecker <brobecker@adacore.com>
Subject: Re: GDB 13 release -- 2023-01-29 Update
Date: Tue, 31 Jan 2023 11:25:05 +0400 [thread overview]
Message-ID: <Y9jCUWq76vTCF/r5@adacore.com> (raw)
In-Reply-To: <87a61zontt.fsf@tromey.com>
Hey Tom!
> Joel> * [TomT] build/29966
> Joel> Cannot build anymore for win32 thread model of gdb
> Joel> https://sourceware.org/bugzilla/show_bug.cgi?id=29966
>
> Joel> This ticket got closed, and then reopened I am not sure by whom,
> Joel> probably the author. I don't believe there is anything there
> Joel> for us to do, so moving this to the "fixed" section.
>
> I more or less gave up on this one. Maybe the reporter will try again,
> but in any case let's not hold the release for this.
Personally, I think you guys have gone way beyond what I would have
done. I was very impressed with your patience and willingness to help.
Thanks for the confirmation that we shouldn't hold ourselves up
for this one.
> Joel> * [TomT] c++/29896
> Joel> GDB git doesn't recognize template function name
> Joel> https://sourceware.org/bugzilla/show_bug.cgi?id=29896
>
> Joel> Patches pushed, to both master and branch, but unfortunately
> Joel> a regression was found - Tom confirmed and is working on a fix.
> Joel> https://sourceware.org/pipermail/gdb-patches/2023-January/195828.html
> I've pushed the fix to both branches now.
Brilliant. Thanks a lot, Tom!
--
Joel
prev parent reply other threads:[~2023-01-31 7:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-29 11:58 Joel Brobecker
2023-01-30 18:54 ` Tom Tromey
2023-01-31 7:25 ` Joel Brobecker [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=Y9jCUWq76vTCF/r5@adacore.com \
--to=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=tom@tromey.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).