public inbox for glibc-cvs@sourceware.org
help / color / mirror / Atom feed
From: Fangrui Song <maskray@sourceware.org>
To: glibc-cvs@sourceware.org
Subject: [glibc/maskray/clang] manual: Update _TIME_BITS to clarify it's user defined
Date: Tue, 19 Oct 2021 17:01:20 +0000 (GMT)	[thread overview]
Message-ID: <20211019170120.5F24E3857C5F@sourceware.org> (raw)

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

commit ad6feef1b0c2cc6d7ad29c5cc4e14ba16f360f06
Author: Stafford Horne <shorne@gmail.com>
Date:   Fri Oct 15 06:55:31 2021 +0900

    manual: Update _TIME_BITS to clarify it's user defined
    
    The current language reads "This macro determines...", changing to
    "Define this macro...".  This is consistent with other feature macro
    documentation language.
    
    When I first read the previous language it seems to indicate that the
    macro is already defined.  By changing the language to "Define this
    macro..." it's clear that its the user's responsibility to define it.

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

diff --git a/manual/creature.texi b/manual/creature.texi
index c13de52f1f..6193e0735c 100644
--- a/manual/creature.texi
+++ b/manual/creature.texi
@@ -171,8 +171,8 @@ This macro was introduced as part of the Large File Support extension
 @end defvr
 
 @defvr Macro _TIME_BITS
-This macro determines the bit size of @code{time_t}, and therefore the
-bit size of all @code{time_t}-derived types and the prototypes of all
+Define this macro to control the bit size of @code{time_t}, and therefore
+the bit size of all @code{time_t}-derived types and the prototypes of all
 related functions.
 
 @enumerate


                 reply	other threads:[~2021-10-19 17:01 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=20211019170120.5F24E3857C5F@sourceware.org \
    --to=maskray@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).