Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@fencepost.gnu.org>
To: jingham@apple.com
Cc: gdb@sources.redhat.com, nick@nick.uklinux.net
Subject: Re: Output of CLI commands under --interpreter=mi
Date: Wed, 24 Apr 2002 10:35:00 -0000	[thread overview]
Message-ID: <E170QgG-0004AH-00@fencepost.gnu.org> (raw)
In-Reply-To: <ABFF54F0-57A5-11D6-8B7C-00039379E320@apple.com> (message from Jim Ingham on Wed, 24 Apr 2002 10:06:52 -0700)

> Date: Wed, 24 Apr 2002 10:06:52 -0700
> From: Jim Ingham <jingham@apple.com>
> 
> Yeah, the problem is that ripping the bits apart is not trivial either.  
> I will see what I can find time to do later in May.

Thanks!


  reply	other threads:[~2002-04-24 17:35 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1019339155.11340.ezmlm@sources.redhat.com>
2002-04-21 11:47 ` Jim Ingham
2002-04-21 22:51   ` Eli Zaretskii
2002-04-24 10:06     ` Jim Ingham
2002-04-24 10:35       ` Eli Zaretskii [this message]
2002-04-20  0:02 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=E170QgG-0004AH-00@fencepost.gnu.org \
    --to=eliz@fencepost.gnu.org \
    --cc=eliz@is.elta.co.il \
    --cc=gdb@sources.redhat.com \
    --cc=jingham@apple.com \
    --cc=nick@nick.uklinux.net \
    /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