public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "brobecker at gnat dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug build/29791] [13 regression] Many gdbsupport files don't compile on Solaris
Date: Sat, 26 Nov 2022 14:09:20 +0000 [thread overview]
Message-ID: <bug-29791-4717-JtHeEWENrm@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-29791-4717@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=29791
Joel Brobecker <brobecker at gnat dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Target Milestone|13.1 |---
CC| |brobecker at gnat dot com
--- Comment #8 from Joel Brobecker <brobecker at gnat dot com> ---
Since the GDB side of things is now in order and we're keeping this PR open
pending some other analysis, I am removing the target milestone, so as to drop
this PR from the release dashboard.
Another option if you prefer, Rainer, would be to mark this PR as done with
target milestone 13.1, and open a separate PR for the GCC side of things. The
former allows for slightly more structured information, but since I don't think
any release is impacted, I don't see this as being critical.
--
You are receiving this mail because:
You are on the CC list for the bug.
prev parent reply other threads:[~2022-11-26 14:09 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-16 14:41 [Bug build/29791] New: " ro at gcc dot gnu.org
2022-11-16 14:42 ` [Bug build/29791] " ro at gcc dot gnu.org
2022-11-16 14:43 ` ro at gcc dot gnu.org
2022-11-16 14:44 ` ro at gcc dot gnu.org
2022-11-16 19:21 ` tromey at sourceware dot org
2022-11-17 9:55 ` cvs-commit at gcc dot gnu.org
2022-11-18 12:50 ` ro at gcc dot gnu.org
2022-11-18 13:10 ` ro at gcc dot gnu.org
2022-11-20 14:15 ` ro at gcc dot gnu.org
2022-11-26 14:09 ` brobecker at gnat dot com [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=bug-29791-4717-JtHeEWENrm@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=gdb-prs@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).