public inbox for glibc-cvs@sourceware.org
help / color / mirror / Atom feed
From: Paul Eggert <eggert@sourceware.org>
To: glibc-cvs@sourceware.org
Subject: [glibc] manual: fix texinfo typo
Date: Sat,  8 Apr 2023 20:53:54 +0000 (GMT)	[thread overview]
Message-ID: <20230408205354.8392B3858D1E@sourceware.org> (raw)

https://sourceware.org/git/gitweb.cgi?p=glibc.git;h=a778333951a2ae530dde8ff18a275155c478aec2

commit a778333951a2ae530dde8ff18a275155c478aec2
Author: Paul Eggert <eggert@cs.ucla.edu>
Date:   Sat Apr 8 13:51:26 2023 -0700

    manual: fix texinfo typo
    
    * manual/creature.texi (Feature Test Macros): Fix
    “creature.texi:309: warning: `.' or `,' must follow @xref, not f”.

Diff:
---
 manual/creature.texi | 3 +--
 1 file changed, 1 insertion(+), 2 deletions(-)

diff --git a/manual/creature.texi b/manual/creature.texi
index 47d1fc4607..fa5dd9d6ad 100644
--- a/manual/creature.texi
+++ b/manual/creature.texi
@@ -306,8 +306,7 @@ If this macro is defined to @math{1}, security hardening is added to
 various library functions.  If defined to @math{2}, even stricter
 checks are applied. If defined to @math{3}, @theglibc{} may also use
 checks that may have an additional performance overhead.
-@xref{Source Fortification,,Fortification of function calls} for more
-information.
+@xref{Source Fortification,,Fortification of function calls}.
 @end defvr
 
 @defvr Macro _DYNAMIC_STACK_SIZE_SOURCE

                 reply	other threads:[~2023-04-08 20:53 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=20230408205354.8392B3858D1E@sourceware.org \
    --to=eggert@sourceware.org \
    --cc=glibc-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).