From: Eli Zaretskii <eliz@gnu.org>
To: "Schimpe, Christina" <christina.schimpe@intel.com>
Cc: gdb-patches@sourceware.org, brobecker@adacore.com
Subject: Re: [PATCH 1/1] gdb: Deprecate MPX commands.
Date: Thu, 07 Mar 2024 15:10:57 +0200 [thread overview]
Message-ID: <86y1au1926.fsf@gnu.org> (raw)
In-Reply-To: <SN7PR11MB7638D28330233BDC37599E15F9202@SN7PR11MB7638.namprd11.prod.outlook.com> (christina.schimpe@intel.com)
> From: "Schimpe, Christina" <christina.schimpe@intel.com>
> CC: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>,
> "brobecker@adacore.com" <brobecker@adacore.com>
> Date: Thu, 7 Mar 2024 12:40:08 +0000
>
> > "Will be removed" or "might be removed"? IOW, are we certain we will
> > definitely remove this, or do we just want to warn users that we might?
>
> Our goal would be to deprecate the MPX commands for gdb 15, if possible.
> Please let me know if there is a problem with that or if there is something required to track this properly for gdb 15. I am not familiar with the procedure. I am adding Joel due to that to this conversation.
>
> We would like to remove MPX for gdb 16. So yes, we certainly will remove MPX. Hopefully for gdb 16 already.
That's fine by me. I just know from experience that deprecated
features can stay in GDB for many years, sometimes indefinitely. But
if we indeed intend to remove the command, the text you proposed for
the manual is okay.
Thanks.
next prev parent reply other threads:[~2024-03-07 13:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-07 12:11 Schimpe, Christina
2024-03-07 12:34 ` Eli Zaretskii
2024-03-07 12:40 ` Schimpe, Christina
2024-03-07 13:10 ` Eli Zaretskii [this message]
2024-03-07 13:30 ` Joel Brobecker
2024-03-08 16:20 ` Tom Tromey
2024-03-12 14:35 ` Schimpe, Christina
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=86y1au1926.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=brobecker@adacore.com \
--cc=christina.schimpe@intel.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).