From: Jacob Bachmeyer <jcb62281@gmail.com>
To: Gavin Smith <GavinSmith0123@gmail.com>,
Jonathan Wakely <jwakely.gcc@gmail.com>,
Richard Stallman <rms@gnu.org>,
bug-texinfo@gnu.org, gcc@gcc.gnu.org
Subject: Re: Makeinfo generates wrong link
Date: Mon, 03 Oct 2022 23:45:57 -0500 [thread overview]
Message-ID: <633BBA85.1070709@gmail.com> (raw)
In-Reply-To: <Yzr4Igz76hPvB+lh@starmint>
Gavin Smith wrote:
> On Mon, Oct 03, 2022 at 08:31:06AM +0100, Jonathan Wakely wrote:
>
>> On Mon, 3 Oct 2022 at 07:01, Gavin Smith via Gcc <gcc@gcc.gnu.org> wrote:
>>
>>> On Sun, Oct 02, 2022 at 09:06:06PM -0400, Richard Stallman wrote:
>>>
>>> [...]
>>> The gcc developers need to provide a stable, version-independent link
>>> for the manual. This link would have worked in the past, but I don't
>>> know how recently it broke.
>>>
>> The URL https://gcc.gnu.org/onlinedocs/cpp/System-specific-Predefined-Macros.html
>> has been stable for many years.
>>
>
> In that case it is the input that is wrong:
>
> Some macros are predefined on each kind of machine
> (@pxref{System-specific Predefined Macros, System-specific Predefined
> Macros, System-specific Predefined Macros, gcc, Using the GNU Compiler
> Collection}). This allows you to provide code specially tuned for a
> particular machine.
>
> It should be
>
> Some macros are predefined on each kind of machine
> (@pxref{System specific Predefined Macros, System specific Predefined
> Macros, System-specific Predefined Macros, gcc, Using the GNU Compiler
> Collection}). This allows you to provide code specially tuned for a
> particular machine.
>
> changing the hyphen to a space in "System specific".
>
There is one additional error here if the above-mentioned URL is
correct: the reference should point to the (cpp) manual instead of the
(gcc) manual.
-- Jacob
next prev parent reply other threads:[~2022-10-04 4:46 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E1of9uI-0004mn-Ep@fencepost.gnu.org>
2022-10-03 6:00 ` Gavin Smith
2022-10-03 7:31 ` Jonathan Wakely
2022-10-03 8:23 ` Jonathan Wakely
2022-10-03 14:56 ` Gavin Smith
2022-10-04 1:02 ` Richard Stallman
2022-10-04 4:45 ` Jacob Bachmeyer [this message]
2022-10-04 17:39 ` Richard Stallman
2022-10-04 19:41 ` Gavin Smith
2022-10-04 20:28 ` Jonathan Wakely
2022-10-10 22:03 ` Richard Stallman
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=633BBA85.1070709@gmail.com \
--to=jcb62281@gmail.com \
--cc=GavinSmith0123@gmail.com \
--cc=bug-texinfo@gnu.org \
--cc=gcc@gcc.gnu.org \
--cc=jwakely.gcc@gmail.com \
--cc=rms@gnu.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).