From: Eli Zaretskii <eliz@gnu.org>
To: Andreas Arnez <arnez@linux.vnet.ibm.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH v3 1/2] Add new GDB command "maint print user-registers"
Date: Wed, 10 Dec 2014 18:14:00 -0000 [thread overview]
Message-ID: <83zjavtm0s.fsf@gnu.org> (raw)
In-Reply-To: <1418232159-15289-2-git-send-email-arnez@linux.vnet.ibm.com>
> From: Andreas Arnez <arnez@linux.vnet.ibm.com>
> Date: Wed, 10 Dec 2014 18:22:38 +0100
>
> This adds a command for listing the "user" registers. So far GDB
> offered no means of determining the set of user registers and omitted
> them from all other register listings.
Thanks.
> +@kindex maint print user-registers
> +@cindex user registers
> +@item maint print user-registers
> +List all currently available ``user'' registers. User registers
When you first introduce new terminology, it is best to use @dfn, like
this:
List all currently available @dfn{user registers}.
This will look prettier in print, and will have the same effect as
``..'' in the Info manual.
Other than that, the documentation parts are OK.
next prev parent reply other threads:[~2014-12-10 18:14 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-10 17:22 [PATCH v3 0/2] Provide useful completer for "info registers" Andreas Arnez
2014-12-10 17:22 ` [PATCH v3 1/2] Add new GDB command "maint print user-registers" Andreas Arnez
2014-12-10 17:38 ` Doug Evans
2014-12-10 18:29 ` Andreas Arnez
2014-12-11 18:35 ` Doug Evans
2014-12-10 18:14 ` Eli Zaretskii [this message]
2014-12-10 18:33 ` Andreas Arnez
2014-12-10 17:22 ` [PATCH v3 2/2] Provide completer for "info registers" Andreas Arnez
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=83zjavtm0s.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=arnez@linux.vnet.ibm.com \
--cc=gdb-patches@sourceware.org \
/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