From: Yao Qi <yao@codesourcery.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: <gdb-patches@sourceware.org>
Subject: Re: [PATCH 2/2] Doc 'dynamic' for command -var-list-children
Date: Thu, 21 Nov 2013 03:52:00 -0000 [thread overview]
Message-ID: <528D7E93.8070201@codesourcery.com> (raw)
In-Reply-To: <83r4acfju4.fsf@gnu.org>
On 11/20/2013 12:16 AM, Eli Zaretskii wrote:
> The patch is OK, but I wonder why we use "1" and not something like
> "true" or "yes".
I don't know, go through the archive, and find that part was added by
"dynamic varobj" patch. Don't see anything on why "1" is used, but I
guess it follows the way how "frozen" is displayed.
Patch is committed.
--
Yao (é½å°§)
next prev parent reply other threads:[~2013-11-21 3:33 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-19 11:39 [PATCH 1/2] Update doc on displayhint in " Yao Qi
2013-11-19 11:31 ` [PATCH 2/2] Doc 'dynamic' for " Yao Qi
2013-11-19 16:17 ` Eli Zaretskii
2013-11-21 3:52 ` Yao Qi [this message]
2013-11-19 16:22 ` [PATCH 1/2] Update doc on displayhint in " Eli Zaretskii
2013-11-19 17:05 ` Tom Tromey
2013-11-20 2:16 ` Yao Qi
2013-11-22 20:02 ` Tom Tromey
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=528D7E93.8070201@codesourcery.com \
--to=yao@codesourcery.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