public inbox for gdb-cvs@sourceware.org
help / color / mirror / Atom feed
From: Tom Tromey <tromey@sourceware.org>
To: gdb-cvs@sourceware.org
Subject: [binutils-gdb] Remove class_pseudo
Date: Sun, 26 Apr 2020 19:48:16 +0000 (GMT)	[thread overview]
Message-ID: <20200426194816.6A172385DC1B@sourceware.org> (raw)

https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=361ba0e891438a44a95206db615d476bea811bac

commit 361ba0e891438a44a95206db615d476bea811bac
Author: Tom Tromey <tom@tromey.com>
Date:   Sun Apr 26 13:36:04 2020 -0600

    Remove class_pseudo
    
    The class_pseudo constant is unused, so this removes it.
    Tested by rebuilding.
    
    gdb/ChangeLog
    2020-04-26  Tom Tromey  <tom@tromey.com>
    
            * command.h (enum command_class) <class_pseudo>: Remove.

Diff:
---
 gdb/ChangeLog | 4 ++++
 gdb/command.h | 2 +-
 2 files changed, 5 insertions(+), 1 deletion(-)

diff --git a/gdb/ChangeLog b/gdb/ChangeLog
index 8186fef88e3..51f4d9595e2 100644
--- a/gdb/ChangeLog
+++ b/gdb/ChangeLog
@@ -1,3 +1,7 @@
+2020-04-26  Tom Tromey  <tom@tromey.com>
+
+	* command.h (enum command_class) <class_pseudo>: Remove.
+
 2020-04-26  Philippe Waroquiers  <philippe.waroquiers@skynet.be>
 
 	* cli/cli-decode.c (lookup_cmd_composition): Fix comments
diff --git a/gdb/command.h b/gdb/command.h
index b9b94227b9f..81c35c98d2f 100644
--- a/gdb/command.h
+++ b/gdb/command.h
@@ -41,7 +41,7 @@ enum command_class
   no_class = -1, class_run = 0, class_vars, class_stack, class_files,
   class_support, class_info, class_breakpoint, class_trace,
   class_alias, class_bookmark, class_obscure, class_maintenance,
-  class_pseudo, class_tui, class_user, class_xdb,
+  class_tui, class_user, class_xdb,
   no_set_class	/* Used for "show" commands that have no corresponding
 		   "set" command.  */
 };


                 reply	other threads:[~2020-04-26 19:48 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=20200426194816.6A172385DC1B@sourceware.org \
    --to=tromey@sourceware.org \
    --cc=gdb-cvs@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).