From: Daniel Jacobowitz <drow@false.org>
To: Kevin Buettner <kevinb@redhat.com>
Cc: gdb@sources.redhat.com
Subject: Re: Redundancy in remote.c packet config messages?
Date: Wed, 06 Apr 2005 21:28:00 -0000 [thread overview]
Message-ID: <20050406212825.GA23835@nevyn.them.org> (raw)
In-Reply-To: <20050406142359.0c61c694@ironwood.lan>
On Wed, Apr 06, 2005 at 02:23:59PM -0700, Kevin Buettner wrote:
> Does anyone know of a case where the first line provides non-redundant
> information? If not, I'd like to prepare a patch which eliminates it.
> That is, I would like the above session to instead show the following
> output:
>
> (gdb) show remote p-packet
> Support for remote protocol `p' (fetch-register) packet is auto-detected,
> currently unknown.
>
> (gdb) set remote p-packet on
> (gdb) show remote p-packet
> Support for remote protocol `p' (fetch-register) packet is currently
> enabled.
> (gdb) set remote p-packet off
> (gdb) show remote p-packet
> Support for remote protocol `p' (fetch-register) packet is currently
> disabled.
I'm pretty sure it will never show useful information. Both lines do
seem to be printing config->detect...
--
Daniel Jacobowitz
CodeSourcery, LLC
prev parent reply other threads:[~2005-04-06 21:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-06 21:24 Kevin Buettner
2005-04-06 21:28 ` Daniel Jacobowitz [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=20050406212825.GA23835@nevyn.them.org \
--to=drow@false.org \
--cc=gdb@sources.redhat.com \
--cc=kevinb@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