public inbox for newlib-cvs@sourceware.org
help / color / mirror / Atom feed
From: Michael Frysinger <vapier@sourceware.org>
To: newlib-cvs@sourceware.org
Subject: [newlib-cygwin] newlib: info: tweak iconv node to avoid collisions
Date: Tue, 13 Dec 2022 10:22:30 +0000 (GMT)	[thread overview]
Message-ID: <20221213102230.946893871D32@sourceware.org> (raw)

https://sourceware.org/git/gitweb.cgi?p=newlib-cygwin.git;h=c8d521033751fbcccdc8ce93f22521e32c6fc6ed

commit c8d521033751fbcccdc8ce93f22521e32c6fc6ed
Author: Mike Frysinger <vapier@gentoo.org>
Date:   Sat Dec 10 03:27:58 2022 -0500

    newlib: info: tweak iconv node to avoid collisions
    
    We have "Iconv" and "iconv" nodes which generates Iconv.html and
    iconv.html files.  On a case-insensitive filesystem, these collide.
    Rename the "Iconv" node to match the chapter name that it's already
    using to avoid the issue.

Diff:
---
 newlib/libc/iconv/iconv.tex | 2 +-
 newlib/libc/libc.texi       | 2 +-
 2 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/newlib/libc/iconv/iconv.tex b/newlib/libc/iconv/iconv.tex
index 42d04c0b6..5b1f7518a 100644
--- a/newlib/libc/iconv/iconv.tex
+++ b/newlib/libc/iconv/iconv.tex
@@ -1,4 +1,4 @@
-@node Iconv
+@node Encoding conversions
 @chapter Encoding conversions (@file{iconv.h})
 
 This chapter describes the Newlib iconv library.
diff --git a/newlib/libc/libc.texi b/newlib/libc/libc.texi
index d217d8118..72328e148 100644
--- a/newlib/libc/libc.texi
+++ b/newlib/libc/libc.texi
@@ -151,7 +151,7 @@ into another language, under the above conditions for modified versions.
 * Posix::
 * Syscalls::
 * Arglists::
-* Iconv::
+* Encoding conversions::
 * Overflow Protection::
 
 * Document Index::

                 reply	other threads:[~2022-12-13 10:22 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20221213102230.946893871D32@sourceware.org \
    --to=vapier@sourceware.org \
    --cc=newlib-cvs@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).