From: Pedro Alves <pedro@palves.net>
To: "gdb@sourceware.org" <gdb@sourceware.org>
Subject: Remove GDB support for S+core
Date: Wed, 16 Mar 2022 14:49:23 +0000 [thread overview]
Message-ID: <397dd08c-eb62-4d6c-33f7-ad9a22a864bd@palves.net> (raw)
FYI, a few years back, we agreed about dropping GDB support for S+core:
https://sourceware.org/pipermail/gdb/2014-October/044643.html
... but then we never acted on it.
I'm finally following through this time, here:
https://sourceware.org/pipermail/gdb-patches/2022-March/186685.html
reply other threads:[~2022-03-16 14:49 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=397dd08c-eb62-4d6c-33f7-ad9a22a864bd@palves.net \
--to=pedro@palves.net \
--cc=gdb@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).