From: Tom Tromey <tom@tromey.com>
To: Tom Tromey via Gdb-patches <gdb-patches@sourceware.org>
Cc: Tom Tromey <tromey@adacore.com>
Subject: Re: [PATCH 0/4] Minor 'struct ui' cleanups
Date: Mon, 18 Jul 2022 08:55:13 -0600 [thread overview]
Message-ID: <878roqmpwu.fsf@tromey.com> (raw)
In-Reply-To: <20220705171532.1072851-1-tromey@adacore.com> (Tom Tromey via Gdb-patches's message of "Tue, 5 Jul 2022 11:15:28 -0600")
>>>>> Tom Tromey via Gdb-patches <gdb-patches@sourceware.org> writes:
> While looking into gdb 'struct ui' handling, I found a few spots that
> could be cleaned up.
> Regression tested on x86-64 Fedora 34.
I'm checking these in.
Tom
prev parent reply other threads:[~2022-07-18 14:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-05 17:15 Tom Tromey
2022-07-05 17:15 ` [PATCH 1/4] Remove ui_register_input_event_handler Tom Tromey
2022-07-05 17:15 ` [PATCH 2/4] Replace input_interactive_p with a method Tom Tromey
2022-07-05 17:15 ` [PATCH 3/4] Remove cli_out_new Tom Tromey
2022-07-05 17:15 ` [PATCH 4/4] Remove manual lifetime management from cli_interp Tom Tromey
2022-07-18 14:55 ` 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=878roqmpwu.fsf@tromey.com \
--to=tom@tromey.com \
--cc=gdb-patches@sourceware.org \
--cc=tromey@adacore.com \
/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).