Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
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: Tue, 07 Aug 2012 01:10:00 -0000	[thread overview]
Message-ID: <5467545.tZipNbH8yO@qiyao.dyndns.org> (raw)
In-Reply-To: <83obmo9eoi.fsf@gnu.org>

On Monday, August 06, 2012 07:18:53 PM Eli Zaretskii wrote:
> When you cannot find a subcommand in the index, you should go for its
> parent command.
> 
> > 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.
> 
> The criteria for kindex is to index every command, but not necessarily
> every subcommand.  So "set remote" is indexed.
> 

OK, the criteria is fine with me.

> Another example of a command with lots of subcommands which are not
> indexed is "set print" (although I see that a couple of subcommands
> sneaked in).
> 
> Again, having lots of index entries with identical beginning pointing
> to the same page is not useful.  Think how this looks in the printed
> manual, for example.
> 
> OK?

The following is to revert my patch.

-- 
Yao (齐尧)

gdb/doc:

2012-08-07  Yao Qi  <yao@codesourcery.com>

	Revert the folloing patch:
	2012-08-06  Yao Qi  <yao@codesourcery.com>
	* gdb.texinfo (Remote Configuration): Add kindex for 'set
	remote hardware-watchpoint-limit' and 'set
	remote hardware-breakpoint-limit'.

Index: doc/gdb.texinfo
===================================================================
RCS file: /cvs/src/src/gdb/doc/gdb.texinfo,v
retrieving revision 1.997
diff -u -r1.997 gdb.texinfo
--- doc/gdb.texinfo	6 Aug 2012 17:13:27 -0000	1.997
+++ doc/gdb.texinfo	7 Aug 2012 01:08:58 -0000
@@ -17839,9 +17839,7 @@
 @anchor{set remote hardware-watchpoint-limit}
 @anchor{set remote hardware-breakpoint-limit}
 @item set remote hardware-watchpoint-limit @var{limit}
-@kindex set remote hardware-watchpoint-limit
 @itemx set remote hardware-breakpoint-limit @var{limit}
-@kindex set remote hardware-breakpoint-limit
 Restrict @value{GDBN} to using @var{limit} remote hardware breakpoint or
 watchpoints.  A limit of -1, the default, is treated as unlimited.


  reply	other threads:[~2012-08-07  1:10 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
2012-08-06 16:19     ` Eli Zaretskii
2012-08-07  1:10       ` Yao Qi [this message]
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=5467545.tZipNbH8yO@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