From: Eli Zaretskii <eliz@gnu.org>
To: Terry Guo <terry.guo@arm.com>
Cc: brobecker@adacore.com, joseph@codesourcery.com,
gdb-patches@sourceware.org, michael.hope@linaro.org
Subject: Re: [PATCH, doc]: Rename Index node to prevent file collision
Date: Thu, 12 Jul 2012 07:57:00 -0000 [thread overview]
Message-ID: <83bojlbeem.fsf@gnu.org> (raw)
In-Reply-To: <000201cd5f24$1ff8e8c0$5feaba40$%guo@arm.com>
> From: "Terry Guo" <terry.guo@arm.com>
> Cc: <brobecker@adacore.com>,
> <joseph@codesourcery.com>,
> <gdb-patches@sourceware.org>,
> "'Michael Hope'" <michael.hope@linaro.org>
> Date: Wed, 11 Jul 2012 13:14:59 +0800
>
> Hi Eli,
>
> When "make html" for gdbint.texi on case-insensitive Mac OS X, we still meet
> index.html and Index.html issue. Could you please also apply same fix to
> gdbint.texi? Thanks.
Done with the patch below.
2012-07-12 Eli Zaretskii <eliz@gnu.org>
* gdbint.texinfo: Remove @syncodeindex directives that put all the
indices into a single node "Index". Instead, join function and
variable indices into a single index, separate from the concept
index. Requested in
http://sourceware.org/ml/gdb-patches/2012-07/msg00146.html.
(Top): Update the top-level menu: instead of one "Index" there are
now separate entries "Concept Index" and "Function and Variable
Index".
(Concept Index, Function and Variable Index): New nodes.
(Index): Node deleted.
Index: gdbint.texinfo
===================================================================
RCS file: /cvs/src/src/gdb/doc/gdbint.texinfo,v
retrieving revision 1.338
diff -u -r1.338 gdbint.texinfo
--- gdbint.texinfo 15 Jun 2012 09:21:36 -0000 1.338
+++ gdbint.texinfo 12 Jul 2012 07:55:15 -0000
@@ -28,9 +28,7 @@
@insertcopying
@end ifnottex
-
-@syncodeindex fn cp
-@syncodeindex vr cp
+@syncodeindex vr fn
@titlepage
@title @value{GDBN} Internals
@@ -93,7 +91,8 @@
* GDB Observers:: @value{GDBN} Currently available observers
* GNU Free Documentation License:: The license for this documentation
-* Index::
+* Concept Index::
+* Function and Variable Index::
@end menu
@node Summary
@@ -8132,9 +8131,14 @@
@appendix GNU Free Documentation License
@include fdl.texi
-@node Index
-@unnumbered Index
+@node Concept Index
+@unnumbered Concept Index
@printindex cp
+@node Function and Variable Index
+@unnumbered Function and Variable Index
+
+@printindex fn
+
@bye
next prev parent reply other threads:[~2012-07-12 7:57 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-14 2:39 Michael Hope
2012-06-14 15:06 ` Joseph S. Myers
2012-06-14 16:42 ` Eli Zaretskii
2012-06-14 21:43 ` Michael Hope
2012-06-14 22:01 ` Joel Brobecker
2012-06-14 22:27 ` Michael Hope
2012-06-15 7:44 ` Eli Zaretskii
2012-06-15 7:36 ` Eli Zaretskii
2012-06-15 12:19 ` Joel Brobecker
2012-06-17 23:26 ` Michael Hope
2012-06-18 2:53 ` Eli Zaretskii
2012-06-21 4:20 ` Michael Hope
2012-06-21 16:22 ` Eli Zaretskii
2012-06-21 22:36 ` Michael Hope
2012-06-22 5:58 ` Eli Zaretskii
2012-06-22 10:03 ` Eli Zaretskii
2012-07-01 19:56 ` Eli Zaretskii
2012-07-02 1:03 ` Michael Hope
2012-07-03 16:23 ` Eli Zaretskii
2012-07-11 5:14 ` Terry Guo
[not found] ` <000201cd5f24$1ff8e8c0$5feaba40$%guo@arm.com>
2012-07-12 7:57 ` Eli Zaretskii [this message]
2012-06-15 7:29 ` Eli Zaretskii
2012-06-17 23:18 ` Michael Hope
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=83bojlbeem.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=joseph@codesourcery.com \
--cc=michael.hope@linaro.org \
--cc=terry.guo@arm.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