From: Yao Qi <yao@codesourcery.com>
To: <gdb-patches@sourceware.org>, Eli Zaretskii <eliz@gnu.org>
Subject: Re: [obv] add kindex for set remote hardware-{watchpoint,breakpoint}-limit
Date: Mon, 06 Aug 2012 15:29:00 -0000 [thread overview]
Message-ID: <1981863.INEZdKZT0P@qiyao.dyndns.org> (raw)
In-Reply-To: <83ipd0au60.fsf@gnu.org>
On Friday, August 03, 2012 06:09:59 PM Eli Zaretskii wrote:
> Sorry, but it isn't obvious. You will see that this whole node has
> only one kindex entry: "@kindex set remote". There are other "set
> remote SOMETHING" commands described there, but none of them has a
> @kindex entry.
>
> The reason for that is simple: it is not useful to have several index
> entries that all begin with the same string and all point to the same
> page.
Hi, Eli,
The reason I post this patch is that I was unable to find 'set remote
hardware-breakpoint-limit' in 'Command and Variable Index'. I thought we need
kindex for *every* command in documentation, and that is why we need "index".
Otherwise, the criteria of using kindex is not clear, IMO.
--
Yao (齐尧)
next prev parent reply other threads:[~2012-08-06 15:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-03 15:00 Yao Qi
2012-08-03 15:10 ` Eli Zaretskii
2012-08-06 15:29 ` Yao Qi [this message]
2012-08-06 16:19 ` Eli Zaretskii
2012-08-07 1:10 ` Yao Qi
2012-08-07 2:52 ` Eli Zaretskii
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=1981863.INEZdKZT0P@qiyao.dyndns.org \
--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