From: Simon Marchi <simark@simark.ca>
To: Tom Tromey <tom@tromey.com>,
Simon Marchi via Gdb-patches <gdb-patches@sourceware.org>
Cc: Simon Marchi <simon.marchi@efficios.com>
Subject: Re: [PATCH] gdb: remove unnecessary tui directory check in configure
Date: Tue, 14 Feb 2023 13:33:04 -0500 [thread overview]
Message-ID: <62f49f4e-0ec7-6433-89c9-b60422d477ec@simark.ca> (raw)
In-Reply-To: <87sff8rvvj.fsf@tromey.com>
On 2/14/23 12:37, Tom Tromey wrote:
>>>>>> "Simon" == Simon Marchi via Gdb-patches <gdb-patches@sourceware.org> writes:
>
> Simon> I suppose this was possible in the CVS days for the tui directory to be
> Simon> missing, but it's not really possible nowaday. Well, a user could
> Simon> delete the directory from their source tree but... it doesn't make
> Simon> sense. Remove the check for that directory in configure.
>
> Thank you.
> Approved-By: Tom Tromey <tom@tromey.com>
>
> Tom
Pushed, thanks.
Simon
prev parent reply other threads:[~2023-02-14 18:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-14 16:37 Simon Marchi
2023-02-14 17:37 ` Tom Tromey
2023-02-14 18:33 ` Simon Marchi [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=62f49f4e-0ec7-6433-89c9-b60422d477ec@simark.ca \
--to=simark@simark.ca \
--cc=gdb-patches@sourceware.org \
--cc=simon.marchi@efficios.com \
--cc=tom@tromey.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).