From: Tom Tromey <tom@tromey.com>
To: Tom Tromey <tom@tromey.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH 0/3] More TUI improvements
Date: Sun, 19 Jan 2020 20:10:00 -0000 [thread overview]
Message-ID: <8736cb43by.fsf@tromey.com> (raw)
In-Reply-To: <20191227235034.5453-1-tom@tromey.com> (Tom Tromey's message of "Fri, 27 Dec 2019 16:50:31 -0700")
>>>>> "Tom" == Tom Tromey <tom@tromey.com> writes:
Tom> This series holds a few TUI improvements.
Tom> Patch 1 is just a bug fix. Patch 2 changes the behavior in a visible
Tom> way, so please give it some thought. Patch 3 is a visual
Tom> optimization.
Tom> Tested on x86-64 Fedora 28.
I'm going to check in patch 1 and patch 3, but hold patch 2 for
discussion.
Tom
prev parent reply other threads:[~2020-01-19 20:08 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-27 23:50 Tom Tromey
2019-12-27 23:50 ` [PATCH 1/3] Make "file" clear TUI source window Tom Tromey
2019-12-27 23:50 ` [PATCH 3/3] Remove flickering from the TUI Tom Tromey
2019-12-27 23:50 ` [PATCH 2/3] Make "disassemble" always use TUI disassembly window Tom Tromey
2020-01-19 20:08 ` Tom Tromey
2020-01-20 0:48 ` Andrew Burgess
2020-01-23 19:54 ` Tom Tromey
2020-01-19 20:10 ` Tom Tromey [this message]
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=8736cb43by.fsf@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).