Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@is.elta.co.il>
To: Andrew Cagney <ac131313@redhat.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [patch/rfc; rfa:doco] Add reggroups and their maint commands
Date: Tue, 22 Oct 2002 23:11:00 -0000	[thread overview]
Message-ID: <Pine.SUN.3.91.1021023080803.13511F@is> (raw)
In-Reply-To: <3DB5F04A.2090005@redhat.com>


On Tue, 22 Oct 2002, Andrew Cagney wrote:

> Eli, now does the revised doco look?

Okay, but I have a couple of comments:

> +the raw register cache; the command @samp{maint print cooked-registers}

Don't we use @code for command names in the user manual?

> +@table @samp
> +@item float_reggroup

I think @table @code is better here (the quotes produced by @samp in 
print are redundant).

Also, I suggest a "@cindex register groups" in gdbint.texinfo where you 
describe the related functions.

Thanks.


  reply	other threads:[~2002-10-23  6:11 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-22 17:41 Andrew Cagney
2002-10-22 23:11 ` Eli Zaretskii [this message]
2003-01-29 16:11   ` Andrew Cagney
2002-11-02  7:16 ` Andrew Cagney

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=Pine.SUN.3.91.1021023080803.13511F@is \
    --to=eliz@is.elta.co.il \
    --cc=ac131313@redhat.com \
    --cc=gdb-patches@sources.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