Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Bob Wilson <bwilson@tensilica.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [PATCH] print message when TUI not configured
Date: Fri, 11 May 2007 18:10:00 -0000	[thread overview]
Message-ID: <4644B1AB.2020502@tensilica.com> (raw)
In-Reply-To: <uhcqjfdhx.fsf@gnu.org>

[-- Attachment #1: Type: text/plain, Size: 476 bytes --]

Eli Zaretskii wrote:
>> Date: Wed, 09 May 2007 14:35:58 -0700
>> From: Bob Wilson <bwilson@tensilica.com>
>>
>> 2007-05-09  Bob Wilson  <bob.wilson@acm.org>
>> 	
>> 	* main.c (captured_main): Recognize -tui option and print an error
>> 	message when the TUI is not configured.
> 
> Fine with me, but if this is accepted, I suggest an entry in NEWS.

OK.  How's this?

2007-05-11  Bob Wilson  <bob.wilson@acm.org>

         * NEWS: Mention change in handling the -tui option.


[-- Attachment #2: gdb-NEWS.patch --]
[-- Type: text/x-diff, Size: 583 bytes --]

Index: NEWS
===================================================================
RCS file: /cvs/src/src/gdb/NEWS,v
retrieving revision 1.224
diff -u -r1.224 NEWS
--- NEWS	7 May 2007 11:49:04 -0000	1.224
+++ NEWS	11 May 2007 18:08:15 -0000
@@ -3,6 +3,10 @@
 
 *** Changes since GDB 6.6
 
+* When the Text User Interface (TUI) is not configured, GDB will now
+recognize the -tui command-line option and print a message that the TUI
+is not supported.
+
 * The GDB remote stub, gdbserver, now has lower overhead for high 
 frequency signals (e.g. SIGALRM) via the QPassSignals packet.
 

  reply	other threads:[~2007-05-11 18:10 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-09 21:34 Bob Wilson
2007-05-09 21:36 ` Bob Wilson
2007-05-09 21:42   ` Daniel Jacobowitz
2007-05-11 17:59   ` Eli Zaretskii
2007-05-11 18:10     ` Bob Wilson [this message]
2007-05-11 18:29       ` Eli Zaretskii

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=4644B1AB.2020502@tensilica.com \
    --to=bwilson@tensilica.com \
    --cc=eliz@gnu.org \
    --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