Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Elena Zannoni <ezannoni@redhat.com>
To: Eli Zaretskii <eliz@is.elta.co.il>
Cc: schwab@suse.de, ezannoni@redhat.com, gdb-patches@sources.redhat.com
Subject: Re: make info warnings
Date: Wed, 15 Jan 2003 17:57:00 -0000	[thread overview]
Message-ID: <15909.41480.492992.568410@localhost.redhat.com> (raw)
In-Reply-To: <9743-Wed15Jan2003192623+0200-eliz@is.elta.co.il>

Eli Zaretskii writes:
 > > From: Andreas Schwab <schwab@suse.de>
 > > Date: Wed, 15 Jan 2003 16:58:58 +0100
 > > 
 > > Elena Zannoni <ezannoni@redhat.com> writes:
 > > 
 > > |> these are the lines that generate the warnings.
 > > |> 
 > > |> @item htrace record @var{[data]*}
 > > |> @item htrace rewind @var{[filename]}
 > > |> @item htrace print @var{[start [len]]}
 > > 
 > > IMHO this should be written like this:
 > > 
 > > @item htrace record [@var{data}]*
 > > @item htrace rewind [@var{filename}]
 > > @item htrace print [@var{start} [@var{len}]]
 > 
 > Yes, that's the right fix.  It makes the printed version look better,
 > too.

Ok, here is a patch. I checked it in.

Elena


2003-01-15  Elena Zannoni  <ezannoni@redhat.com>

	(OpenRISC 1000): Fix formatting of command names.

Index: gdb.texinfo
===================================================================
RCS file: /cvs/uberbaum/gdb/doc/gdb.texinfo,v
retrieving revision 1.138
diff -u -p -r1.138 gdb.texinfo
--- gdb.texinfo	15 Jan 2003 14:31:59 -0000	1.138
+++ gdb.texinfo	15 Jan 2003 17:55:36 -0000
@@ -11904,7 +11904,7 @@ Set acquisition qualifier for HW trace.
 Set HW trace stopping criteria.
 
 @kindex htrace record
-@item htrace record @var{[data]*}
+@item htrace record [@var{data}]*
 Selects the data to be recorded, when qualifier is met and HW trace was
 triggered.
 
@@ -11915,14 +11915,14 @@ triggered.
 Enables/disables the HW trace.
 
 @kindex htrace rewind
-@item htrace rewind @var{[filename]}
+@item htrace rewind [@var{filename}]
 Clears currently recorded trace data.
 
 If filename is specified, new trace file is made and any newly collected data
 will be written there.
 
 @kindex htrace print
-@item htrace print @var{[start [len]]}
+@item htrace print [@var{start} [@var{len}]]
 Prints trace buffer, using current record configuration.
 
 @kindex htrace mode continuous


  reply	other threads:[~2003-01-15 17:57 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-15 14:47 Elena Zannoni
2003-01-15 15:59 ` Andreas Schwab
2003-01-15 17:28   ` Eli Zaretskii
2003-01-15 17:57     ` Elena Zannoni [this message]
2003-01-15 17:52   ` Elena Zannoni
2003-01-15 16:39 Michael Elizabeth Chastain

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=15909.41480.492992.568410@localhost.redhat.com \
    --to=ezannoni@redhat.com \
    --cc=eliz@is.elta.co.il \
    --cc=gdb-patches@sources.redhat.com \
    --cc=schwab@suse.de \
    /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