From: Eli Zaretskii <eliz@gnu.org>
To: Luis Machado <lgustavo@codesourcery.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH 3/3] Documentation changes for the new zhexadecimal format
Date: Wed, 06 May 2015 15:36:00 -0000 [thread overview]
Message-ID: <83sib9ra4w.fsf@gnu.org> (raw)
In-Reply-To: <554A1D90.10707@codesourcery.com>
> Date: Wed, 6 May 2015 10:56:32 -0300
> From: Luis Machado <lgustavo@codesourcery.com>
> CC: <gdb-patches@sourceware.org>
>
> On 05/01/2015 12:07 PM, Eli Zaretskii wrote:
> >> From: Luis Machado <lgustavo@codesourcery.com>
> >> Date: Fri, 1 May 2015 11:32:38 -0300
> >>
> >> This patch updates the documentation to reflect the addition of the new
> >> zhexadecimal format option for -var-set-format and also adds a NEWS entry
> >> for the change.
> >
> > OK, but should we perhaps explain what zhexadecimal means? I didn't
> > know about it until I read this patch.
>
> I'm not too sure where that explanation should go.
It should be near the first use of this term.
> What about 'zero-padded-hexadecimal'? Too long?
Yes, and I don't think we should go to such extremes. Just explaining
the term the first time it is used in the manual should be OK.
prev parent reply other threads:[~2015-05-06 15:36 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-01 14:32 [PATCH 0/3] varobj zero-padded hexadecimal format Luis Machado
2015-05-01 14:32 ` [PATCH 1/3] Add zero-padded hexadecimal format support for varobj's Luis Machado
2015-05-01 14:33 ` [PATCH 2/3] Add varobj zhexadecimal format tests Luis Machado
2015-05-01 14:33 ` [PATCH 3/3] Documentation changes for the new zhexadecimal format Luis Machado
2015-05-01 15:07 ` Eli Zaretskii
2015-05-01 18:58 ` Luis Machado
2015-05-06 13:56 ` Luis Machado
2015-05-06 14:01 ` Luis Machado
2015-05-06 15:36 ` Eli Zaretskii [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=83sib9ra4w.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=lgustavo@codesourcery.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