From: Daniel Jacobowitz <drow@mvista.com>
To: gdb-patches@sources.redhat.com
Subject: Re: [patch/rfc] "tui"
Date: Tue, 10 Feb 2004 18:40:00 -0000 [thread overview]
Message-ID: <20040210184009.GA28778@nevyn.them.org> (raw)
In-Reply-To: <402923AD.7060104@gnu.org>
On Tue, Feb 10, 2004 at 01:32:13PM -0500, Andrew Cagney wrote:
> Hello,
>
> This modifies the build machinery so that the program "tui" is built.
> "tui" starts up GDB's TUI (or Text User Interface). Alternative program
> names include "tgdb", "gdbtui", ...
>
> Comments? Otherwize look to commit it round 16th Feb.
Any of those names sound great to me. I think that one with "gdb" in it
would be clearer; unlike Insight, the TUI does not have a separate life
from GDB.
--
Daniel Jacobowitz
MontaVista Software Debian GNU/Linux Developer
next prev parent reply other threads:[~2004-02-10 18:40 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-10 18:32 Andrew Cagney
2004-02-10 18:40 ` Daniel Jacobowitz [this message]
2004-02-10 19:53 ` Kevin Buettner
2004-02-11 13:11 ` Bob Rossi
2004-02-11 14:47 ` Andrew Cagney
2004-02-11 15:00 ` Bob Rossi
2004-02-12 4:34 ` Christopher Faylor
2004-02-10 19:11 ` Eli Zaretskii
2004-02-10 20:47 ` Andrew Cagney
2004-02-11 6:27 ` Eli Zaretskii
2004-02-18 18:53 ` Andrew Cagney
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=20040210184009.GA28778@nevyn.them.org \
--to=drow@mvista.com \
--cc=gdb-patches@sources.redhat.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