public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Richard Stallman <rms@gnu.org>
To: Gavin Smith <gavinsmith0123@gmail.com>
Cc: GavinSmith0123@gmail.com, jwakely.gcc@gmail.com,
	bug-texinfo@gnu.org, gcc@gcc.gnu.org
Subject: Re: Makeinfo generates wrong link
Date: Mon, 03 Oct 2022 21:02:43 -0400	[thread overview]
Message-ID: <E1ofWKZ-0006SI-0j@fencepost.gnu.org> (raw)
In-Reply-To: <Yzr4Igz76hPvB+lh@starmint> (message from Gavin Smith on Mon, 3 Oct 2022 15:56:34 +0100)

[[[ To any NSA and FBI agents reading my email: please consider    ]]]
[[[ whether defending the US Constitution against all enemies,     ]]]
[[[ foreign or domestic, requires you to follow Snowden's example. ]]]

  >     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".

I will make that change.  Thanks.

-- 
Dr Richard Stallman (https://stallman.org)
Chief GNUisance of the GNU Project (https://gnu.org)
Founder, Free Software Foundation (https://fsf.org)
Internet Hall-of-Famer (https://internethalloffame.org)



  reply	other threads:[~2022-10-04  1:02 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 [this message]
2022-10-04  4:45       ` Jacob Bachmeyer
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=E1ofWKZ-0006SI-0j@fencepost.gnu.org \
    --to=rms@gnu.org \
    --cc=bug-texinfo@gnu.org \
    --cc=gavinsmith0123@gmail.com \
    --cc=gcc@gcc.gnu.org \
    --cc=jwakely.gcc@gmail.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).