Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Michael Hope <michael.hope@linaro.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: "Joseph S. Myers" <joseph@codesourcery.com>, gdb-patches@sourceware.org
Subject: Re: [PATCH, doc]: Rename Index node to prevent file collision
Date: Thu, 14 Jun 2012 21:43:00 -0000	[thread overview]
Message-ID: <CANLjY-nrPVBk1RM7gOo4yhvzFd+agB9Xs=kUAMUJna0LP-voZQ@mail.gmail.com> (raw)
In-Reply-To: <83ehphyhdn.fsf@gnu.org>

On 15 June 2012 04:42, Eli Zaretskii <eliz@gnu.org> wrote:
>> Date: Thu, 14 Jun 2012 15:06:30 +0000 (UTC)
>> From: "Joseph S. Myers" <joseph@codesourcery.com>
>> cc: gdb-patches@sourceware.org
>>
>> On Thu, 14 Jun 2012, Michael Hope wrote:
>>
>> > 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.
>>
>> This was rejected when I submitted it
>> <http://sourceware.org/ml/gdb-patches/2009-01/msg00298.html>.
>
> Right, and I still would like very much to follow GNU practice in this
> matter.
>
> Michael, is your setup also that you produce the HTML files on a Posix
> host, but then deploy them on Windows?

Yip.  We supply pre-built toolchains for Linux and Windows[1].  The
build is crtosstool-NG based, runs on Ubuntu Lucid, and uses the LSB
compilers for Linux and the mingw cross compilers for Windows.  We
cross-make the manuals the same as we cross-build the compiler.

The makeinfo manual says: """If makeinfo is run on a system which does
not distinguish case in filenames, nodes which are the same except for
case will also be folded into the same output file.""".  I don't think
that's valid here as the index is a special case: we shouldn't merge
the top level index.html with the output of a node called Index.

-- Michael


  reply	other threads:[~2012-06-14 21:43 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 [this message]
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='CANLjY-nrPVBk1RM7gOo4yhvzFd+agB9Xs=kUAMUJna0LP-voZQ@mail.gmail.com' \
    --to=michael.hope@linaro.org \
    --cc=eliz@gnu.org \
    --cc=gdb-patches@sourceware.org \
    --cc=joseph@codesourcery.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