Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Michael Hope <michael.hope@linaro.org>
To: gdb-patches@sourceware.org
Subject: [PATCH, doc]: Rename Index node to prevent file collision
Date: Thu, 14 Jun 2012 02:39:00 -0000	[thread overview]
Message-ID: <4FD94EC0.1000009@linaro.org> (raw)

Hi there.  This patch renames the 'Index' node in the GDB end user documentation to 'GDB Index'
to prevent generating HTML filenames that differ only in case.

makeinfo generates a HTML file per node and uses the node name as the filename.  It also generates
a top level 'index.html'.  This causes problems in Windows as 'index.html' and 'Index.html' differ
only in case.

'GDB Index' matches the binutils style of using 'AS Index' and similar for the different tools.
makeinfo displays the node name to the end user in the window title so you can't use names like
'Index_'.

OK for trunk?

-- Michael

2012-06-14  Michael Hope  <michael.hope@linaro.org>

        * gdb.texinfo (GDB Index): Rename 'Index' to 'GDB Index'.

--- a/gdb/doc/gdb.texinfo
+++ b/gdb/doc/gdb.texinfo
@@ -182,7 +182,7 @@ software in general.  We will miss him.
  * Copying::                    GNU General Public License says
                                  how you can copy and share GDB
  * GNU Free Documentation License::  The license for this documentation
-* Index::                       Index
+* GDB Index::                   GDB Index
  @end menu

  @end ifnottex
@@ -1779,7 +1779,7 @@ and @code{show} to inquire about the state of your program, or the state
  of @value{GDBN} itself.  Each command supports many topics of inquiry; this
  manual introduces each of them in the appropriate context.  The listings
  under @code{info} and under @code{show} in the Index point to
-all the sub-commands.  @xref{Index}.
+all the sub-commands.  @xref{GDB Index}.

  @c @group
  @table @code
@@ -40390,8 +40390,8 @@ A string in the constant pool is zero-terminated.
  @appendix GNU Free Documentation License
  @include fdl.texi

-@node Index
-@unnumbered Index
+@node GDB Index
+@unnumbered GDB Index

  @printindex cp


             reply	other threads:[~2012-06-14  2:39 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-14  2:39 Michael Hope [this message]
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
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=4FD94EC0.1000009@linaro.org \
    --to=michael.hope@linaro.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