From: Andrew Cagney <ac131313@redhat.com>
To: Elena Zannoni <ezannoni@redhat.com>
Cc: "J. Johnston" <jjohnstn@redhat.com>, gdb-patches@sources.redhat.com
Subject: Re: patch for gdb/mi 680
Date: Mon, 21 Oct 2002 18:13:00 -0000 [thread overview]
Message-ID: <3DB4A64C.3080102@redhat.com> (raw)
In-Reply-To: <15796.34912.481295.841143@localhost.redhat.com>
> Another thing, are there any more uses of ui_out_tuple_begin
> ui_out_tuple_end, etc? Could the functions be zapped/ifdeffed out, so that
> they are not creep in again?
Definitly a good idea (zap it).
Andrew
prev parent reply other threads:[~2002-10-22 1:13 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-10 14:03 J. Johnston
2002-10-21 16:06 ` Elena Zannoni
2002-10-21 16:08 ` Elena Zannoni
2002-10-21 16:34 ` J. Johnston
2002-10-22 7:20 ` Elena Zannoni
2002-10-23 14:20 ` J. Johnston
2002-10-21 18:13 ` Andrew Cagney [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=3DB4A64C.3080102@redhat.com \
--to=ac131313@redhat.com \
--cc=ezannoni@redhat.com \
--cc=gdb-patches@sources.redhat.com \
--cc=jjohnstn@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