From: Tom Tromey <tom@tromey.com>
To: gdb-patches@sourceware.org
Subject: [PATCH 0/9] Even more TUI refactorings
Date: Fri, 16 Aug 2019 16:15:00 -0000 [thread overview]
Message-ID: <20190816161511.16162-1-tom@tromey.com> (raw)
Here's another round of TUI refactorings.
This series is a bit shorter than the others because I'm trying to
send refactorings separately from behavior-changing patches, and the
next patch after these does change the TUI in a user-visible way.
Each patch was built and tested using the gdb.tui tests.
Tom
next reply other threads:[~2019-08-16 16:15 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-16 16:15 Tom Tromey [this message]
2019-08-16 16:15 ` [PATCH 9/9] Remove useless assignment from tui_remove_hooks Tom Tromey
2019-08-16 16:15 ` [PATCH 7/9] Introduce tui_source_window_base::set_contents method Tom Tromey
2019-08-16 16:15 ` [PATCH 5/9] Change tui_update_source_window to be a method Tom Tromey
2019-08-16 16:15 ` [PATCH 1/9] Remove m_has_locator Tom Tromey
2019-08-16 16:15 ` [PATCH 6/9] Change tui_update_breakpoint_info to be a method Tom Tromey
2019-08-16 16:15 ` [PATCH 8/9] Change tui_show_symtab_source " Tom Tromey
2019-08-16 16:15 ` [PATCH 4/9] Change tui_update_source_window_as_is " Tom Tromey
2019-08-16 16:15 ` [PATCH 3/9] Remove "noerror" parameter from some TUI functions Tom Tromey
2019-08-16 16:15 ` [PATCH 2/9] Remove separate visibility flag Tom Tromey
2019-08-16 16:50 ` [PATCH 0/9] Even more TUI refactorings Pedro Alves
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=20190816161511.16162-1-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).