From: Andreas Arnez <arnez@linux.vnet.ibm.com>
To: Eli Zaretskii <eliz@gnu.org>
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:33:00 -0000 [thread overview]
Message-ID: <87k31zmk1g.fsf@br87z6lw.de.ibm.com> (raw)
In-Reply-To: <83zjavtm0s.fsf@gnu.org> (Eli Zaretskii's message of "Wed, 10 Dec 2014 20:09:07 +0200")
On Wed, Dec 10 2014, Eli Zaretskii wrote:
> 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.
Sure, I will include this change in the next version.
prev parent reply other threads:[~2014-12-10 18:33 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 2/2] Provide " 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
2014-12-10 18:33 ` Andreas Arnez [this message]
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=87k31zmk1g.fsf@br87z6lw.de.ibm.com \
--to=arnez@linux.vnet.ibm.com \
--cc=eliz@gnu.org \
--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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).