From: Joel Brobecker <brobecker@adacore.com>
To: "Schimpe, Christina" <christina.schimpe@intel.com>
Cc: Eli Zaretskii <eliz@gnu.org>,
"gdb-patches@sourceware.org" <gdb-patches@sourceware.org>,
"brobecker@adacore.com" <brobecker@adacore.com>
Subject: Re: [PATCH 1/1] gdb: Deprecate MPX commands.
Date: Thu, 7 Mar 2024 17:30:13 +0400 [thread overview]
Message-ID: <ZenBZa+poGbwIoOU@adacore.com> (raw)
In-Reply-To: <SN7PR11MB7638D28330233BDC37599E15F9202@SN7PR11MB7638.namprd11.prod.outlook.com>
Hello,
> > "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.
This is more a question for the GDB maintainers than for the release
manager, but from memory, I believe the process you're going through,
where you first deprecate the feature and also announce it in the NEWS
for one release and then remove it for the next release, is the process
that we agreed to go through in the GDB project.
--
Joel
next prev parent reply other threads:[~2024-03-07 13:30 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
2024-03-07 13:30 ` Joel Brobecker [this message]
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=ZenBZa+poGbwIoOU@adacore.com \
--to=brobecker@adacore.com \
--cc=christina.schimpe@intel.com \
--cc=eliz@gnu.org \
--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).