From: Eli Zaretskii <eliz@gnu.org>
To: Torbjorn SVENSSON <torbjorn.svensson@foss.st.com>
Cc: gdb-patches@sourceware.org
Subject: Re: Generated GDB documentation have colliding files on a case insensitive files system
Date: Sat, 07 Jan 2023 13:08:56 +0200 [thread overview]
Message-ID: <83sfgmsit3.fsf@gnu.org> (raw)
In-Reply-To: <d538bd53-1428-4234-129e-e7d2978501c1@foss.st.com> (message from Torbjorn SVENSSON on Sat, 7 Jan 2023 11:52:45 +0100)
> Date: Sat, 7 Jan 2023 11:52:45 +0100
> CC: <gdb-patches@sourceware.org>
> From: Torbjorn SVENSSON <torbjorn.svensson@foss.st.com>
>
> On 2023-01-07 11:43, Eli Zaretskii wrote:
> >> Date: Sat, 7 Jan 2023 10:42:11 +0100
> >> CC: <gdb-patches@sourceware.org>
> >> From: Torbjorn SVENSSON <torbjorn.svensson@foss.st.com>
> >>
> >> Do you see any use of the ~214 redirect pages in the GDB context?
> >
> > Sorry, I don't understand the question. What do you mean by "see any
> > use" in this context?
>
> I was considering if the redirect files could simply be removed from the
> GDB documentation tree or if they are actually used for inter components
> references.
They are produced by makeinfo, and they are produced for a reason, no?
> I'm more or less trying to find the best solution for GDB.
>
> There is the possibility to rename one of the [qQ]MemTags anchors in the
> GDB documentation, but that will also include the alternative name in
> the redirect page and it would require all the @xref etc to be updated
> to the renamed anchor.
>
> Even if we get a solution merged in texinfo, it will take years for it
> to get activity used, and in the mean while, we are stuck with this
> issue in GDB.
I still don't want to make any conclusions until the Texinfo
discussion is completed. How do you know there's no solution with the
existing Texinfo versions?
next prev parent reply other threads:[~2023-01-07 11:08 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-07 9:21 Torbjorn SVENSSON
2023-01-07 9:37 ` Eli Zaretskii
2023-01-07 9:42 ` Torbjorn SVENSSON
2023-01-07 10:43 ` Eli Zaretskii
2023-01-07 10:52 ` Torbjorn SVENSSON
2023-01-07 11:08 ` Eli Zaretskii [this message]
2023-01-09 6:51 ` Torbjorn SVENSSON
2023-01-09 12:24 ` Eli Zaretskii
2023-01-15 17:22 ` Torbjorn SVENSSON
2023-01-15 17:39 ` Eli Zaretskii
2023-01-15 17:43 ` Torbjorn SVENSSON
2023-01-15 18:09 ` Eli Zaretskii
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=83sfgmsit3.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=torbjorn.svensson@foss.st.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).