From: Ben Elliston <bje@au1.ibm.com>
To: "Carlos O'Donell" <carlos@codesourcery.com>
Cc: binutils@sourceware.org
Subject: Re: [PATCH] Fix html filenames on case insensitive filesystems.
Date: Mon, 15 May 2006 11:12:00 -0000 [thread overview]
Message-ID: <20060515021115.GA27459@ozlabs.au.ibm.com> (raw)
In-Reply-To: <20060511154503.GC21801@lios>
> The binutils html manuals are built using "makeinfo --html", which
> converts @node names directly into <node>.html when splitting the
> html files. In a case insensitive filesystem this causes certains
> files to conflict.
Perhaps you should report this problem to the Texinfo maintainer, too?
At the very least, makeinfo could complain about this condition. A
better alternative might be to mangle the output filenames a bit so
that the user need not be concerned with this.
Ben
next prev parent reply other threads:[~2006-05-15 3:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-11 20:57 Carlos O'Donell
2006-05-11 21:24 ` Nick Clifton
2006-05-11 21:24 ` Carlos O'Donell
2006-05-15 11:12 ` Ben Elliston [this message]
2006-05-16 23:09 ` Carlos O'Donell
2006-05-17 20:37 ` Nick Clifton
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=20060515021115.GA27459@ozlabs.au.ibm.com \
--to=bje@au1.ibm.com \
--cc=binutils@sourceware.org \
--cc=carlos@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).