From: Joel Brobecker via Gdb <gdb@sourceware.org>
To: Andrew Burgess <aburgess@redhat.com>
Cc: Joel Brobecker <brobecker@adacore.com>, gdb@sourceware.org
Subject: Re: [ANNOUNCEMENT] GDB 16.1 released!
Date: Thu, 23 Jan 2025 10:29:05 +0400 [thread overview]
Message-ID: <Z5HhsTFCEL2m66nd@adacore.com> (raw)
In-Reply-To: <87frlamtml.fsf@redhat.com>
> And we should decide what we want to do about:
>
> https://inbox.sourceware.org/gdb-patches/CAOp6jLYD0g-GUsx7jhO3g8H_4pHkB6dkh51cbyDT-5yMfQwu+A@mail.gmail.com
>
> Before making any follow on release.
Agreed!
Beyond that, we shouldn't worry about the effort needed to create
a new release. It's not that much, especially for corrective releases.
So let's do a quick corrective release once we know more about
this other new issue.
--
Joel
next prev parent reply other threads:[~2025-01-23 6:29 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-18 10:38 Joel Brobecker via Gdb-announce via Gdb
2025-01-21 13:55 ` Andrew Burgess via Gdb
[not found] ` <Z5BiYQ6L6bfNZy3M@adacore.com>
2025-01-22 3:20 ` Joel Brobecker via Gdb
2025-01-22 11:02 ` Andrew Burgess via Gdb
2025-01-22 11:07 ` Joel Brobecker via Gdb
2025-01-22 19:55 ` Andrew Burgess via Gdb
2025-01-22 21:22 ` Andrew Burgess via Gdb
2025-01-23 6:29 ` Joel Brobecker via Gdb [this message]
2025-01-28 13:04 ` Andrew Burgess via Gdb
2025-01-29 5:18 ` Joel Brobecker via Gdb
2025-01-23 18:05 ` Luis Machado via Gdb
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=Z5HhsTFCEL2m66nd@adacore.com \
--to=gdb@sourceware.org \
--cc=aburgess@redhat.com \
--cc=brobecker@adacore.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