Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: "Eli Zaretskii" <eliz@elta.co.il>
To: Nick Roberts <nick@nick.uklinux.net>
Cc: ac131313@redhat.com, jingham@apple.com, gdb-patches@sources.redhat.com
Subject: Re: PATCH (gdb/mi)
Date: Fri, 21 Nov 2003 17:41:00 -0000	[thread overview]
Message-ID: <5769-Fri21Nov2003193941+0200-eliz@elta.co.il> (raw)
In-Reply-To: <16291.61005.91144.786073@nick.uklinux.net> (message from Nick Roberts on Sat, 1 Nov 2003 17:33:01 +0000)

> From: Nick Roberts <nick@nick.uklinux.net>
> Date: Sat, 1 Nov 2003 17:33:01 +0000
> 
>  > - doco
> 
> below

Approved, but please correct this small blunder:

>   @smallexample
> !  -var-list-children @var{name} [PRINT-VALUES]
>   @end smallexample

Since PRINT-VALUES stands for something else, you should use @var,
like this:

   @smallexample
 !  -var-list-children @var{name} [@var{print-values}]
   @end smallexample

> ! Returns a list of the children of the specified variable object.  With
> ! just the variable object name as an argument or with an optional
> ! second argument of 0, prints only the names of the variables.  With an
> ! optional second argument of 1, also prints their values.

If print-values can be only 0 or 1, perhaps it's better to say

  -var-list-children @var{name} [0|1]


  parent reply	other threads:[~2003-11-21 17:41 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1067099552.15608.ezmlm@sources.redhat.com>
2003-10-27 19:02 ` Jim Ingham
2003-10-27 19:52   ` Eli Zaretskii
2003-10-30 21:01   ` Andrew Cagney
2003-10-31 17:57     ` Jim Ingham
2003-11-01 16:40     ` Nick Roberts
2003-11-03 14:35       ` Andrew Cagney
2003-11-21 17:41       ` Eli Zaretskii [this message]
2003-10-28  0:22 Nick Roberts
2003-10-28  6:44 ` Eli Zaretskii
  -- strict thread matches above, loose matches on Subject: below --
2003-10-25 16:32 Nick Roberts

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=5769-Fri21Nov2003193941+0200-eliz@elta.co.il \
    --to=eliz@elta.co.il \
    --cc=ac131313@redhat.com \
    --cc=gdb-patches@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