public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Tom Tromey <tom@tromey.com>
To: gdb-patches@sourceware.org
Cc: Tom Tromey <tom@tromey.com>
Subject: [PATCH 1/6] Remove two TUI comments
Date: Wed, 02 Oct 2019 23:12:00 -0000	[thread overview]
Message-ID: <20191002231202.10940-2-tom@tromey.com> (raw)
In-Reply-To: <20191002231202.10940-1-tom@tromey.com>

This removes two comments from tui.h.  These were not useful.

gdb/ChangeLog
2019-10-02  Tom Tromey  <tom@tromey.com>

	* tui/tui.h: Remove comments.
---
 gdb/ChangeLog | 4 ++++
 gdb/tui/tui.h | 2 --
 2 files changed, 4 insertions(+), 2 deletions(-)

diff --git a/gdb/tui/tui.h b/gdb/tui/tui.h
index baf4a813b60..dac410fcfa1 100644
--- a/gdb/tui/tui.h
+++ b/gdb/tui/tui.h
@@ -45,8 +45,6 @@ enum tui_win_type
   DATA_ITEM_WIN
 };
 
-/* GENERAL TUI FUNCTIONS */
-/* tui.c */
 extern CORE_ADDR tui_get_low_disassembly_address (struct gdbarch *,
 						  CORE_ADDR, CORE_ADDR);
 extern void tui_show_assembly (struct gdbarch *gdbarch, CORE_ADDR addr);
-- 
2.17.2

  parent reply	other threads:[~2019-10-02 23:12 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-02 23:12 [PATCH 0/6] More TUI updates Tom Tromey
2019-10-02 23:12 ` [PATCH 5/6] Make TUI window handle a unique_ptr Tom Tromey
2019-10-02 23:12 ` [PATCH 4/6] Remove declaration from tui-wingeneral.h Tom Tromey
2019-10-02 23:12 ` [PATCH 6/6] Don't call erase_data_content from tui_data_window::show_registers Tom Tromey
2019-10-02 23:12 ` Tom Tromey [this message]
2019-10-02 23:22 ` [PATCH 2/6] Remove tui_default_win_viewport_height Tom Tromey
2019-10-02 23:22 ` [PATCH 3/6] Remove tui_win_is_auxiliary Tom Tromey
2019-10-09 22:50 ` [PATCH 0/6] More TUI updates 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=20191002231202.10940-2-tom@tromey.com \
    --to=tom@tromey.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).