Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: Joel Brobecker <brobecker@adacore.com>
Cc: Stan Shebs <stanshebs@earthlink.net>, gdb-patches@sourceware.org
Subject: [NEWS patch] Re: [patch 1/2] Make gdbtui a shell script
Date: Thu, 22 Dec 2011 10:16:00 -0000	[thread overview]
Message-ID: <20111222101258.GA18148@host2.jankratochvil.net> (raw)
In-Reply-To: <20111222052136.GP23376@adacore.com>

On Thu, 22 Dec 2011 00:11:25 +0100, Stan Shebs wrote:
> It seems a little disruptive to our users and repackagers to have the name
> disappear altogether with no prior warning.

The deprecation NEWS items have been present but TBH as Fedora + RHEL
GDB packager I have no idea what I could do with it in advance.


On Thu, 22 Dec 2011 06:21:36 +0100, Joel Brobecker wrote:
> > Assuming that this patch is only going into trunk, then it seems
> > sufficient to add a news item to 7.4 warning of the coming change,
> > or even adding a deprecation warning to the branch's tui-main, which
> > will give everybody the 7.4 - 7.5 interval to update their usages.
> 
> Works for me!


Thanks,
Jan


gdb/
2011-12-22  Jan Kratochvil  <jan.kratochvil@redhat.com>

	* NEWS (Changes in GDB 7.4): Add gdbtui deprecation note.
	* tui/tui-main.c: Likewise.

--- a/gdb/NEWS
+++ b/gdb/NEWS
@@ -259,6 +259,11 @@ Texas Instruments TMS320C6x		tic6x-*-*
 
 Renesas RL78				rl78-*-elf
 
+* The binary "gdbtui" is deprecated.
+
+The binary will be no longer built or installed in GDB 7.5.  Use "gdb -tui"
+instead.
+
 *** Changes in GDB 7.3.1
 
 * The build failure for NetBSD and OpenBSD targets have now been fixed.
--- a/gdb/tui/tui-main.c
+++ b/gdb/tui/tui-main.c
@@ -18,6 +18,11 @@
    You should have received a copy of the GNU General Public License
    along with this program.  If not, see <http://www.gnu.org/licenses/>.  */
 
+/* The binary "gdbtui" is deprecated.
+
+   The binary will be no longer built or installed in GDB 7.5.  Use "gdb -tui"
+   instead.  */
+
 #include "defs.h"
 #include "main.h"
 #include "gdb_string.h"


  reply	other threads:[~2011-12-22 10:13 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-21 11:47 Jan Kratochvil
2011-12-21 12:53 ` Joel Brobecker
2011-12-21 14:25   ` Jan Kratochvil
2011-12-21 14:32     ` Pierre Muller
2011-12-21 14:39       ` Jan Kratochvil
2011-12-21 17:11         ` Joel Brobecker
2011-12-21 18:37         ` Tom Tromey
2011-12-21 23:11           ` [patch 1/2] Drop gdbtui [+doc changes] Jan Kratochvil
2011-12-22  8:11             ` Eli Zaretskii
2011-12-22  9:53               ` Jan Kratochvil
2011-12-22 11:33                 ` Eli Zaretskii
2011-12-22 17:15                   ` Jan Kratochvil
2012-01-02  2:30             ` [commit] " Jan Kratochvil
2012-01-02 13:03               ` Pedro Alves
2012-01-02 13:32                 ` [commit] Fix/revert insight build regression by me [Re: [commit] [patch 1/2] Drop gdbtui [+doc changes]] Jan Kratochvil
2011-12-21 23:39   ` [patch 1/2] Make gdbtui a shell script Stan Shebs
2011-12-22  6:26     ` Joel Brobecker
2011-12-22 10:16       ` Jan Kratochvil [this message]
2012-01-01 21:52         ` [commit 7.4] [NEWS patch] " Jan Kratochvil
2011-12-21 17:26 ` Tom Tromey

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=20111222101258.GA18148@host2.jankratochvil.net \
    --to=jan.kratochvil@redhat.com \
    --cc=brobecker@adacore.com \
    --cc=gdb-patches@sourceware.org \
    --cc=stanshebs@earthlink.net \
    /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