public inbox for glibc-cvs@sourceware.org
help / color / mirror / Atom feed
From: H.J. Lu <hjl@sourceware.org>
To: glibc-cvs@sourceware.org
Subject: [glibc] string.h: Fix boolean spelling in comments
Date: Fri,  3 Jun 2022 19:13:20 +0000 (GMT)	[thread overview]
Message-ID: <20220603191320.AC15C3858405@sourceware.org> (raw)

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

commit 3c23fa9f44fe88d0851e1344fc37ba60e74cb0fc
Author: H.J. Lu <hjl.tools@gmail.com>
Date:   Fri Jun 3 10:22:38 2022 -0700

    string.h: Fix boolean spelling in comments

Diff:
---
 string/string.h | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/string/string.h b/string/string.h
index d494a1d5f9..54dd8344de 100644
--- a/string/string.h
+++ b/string/string.h
@@ -73,7 +73,7 @@ extern int memcmp (const void *__s1, const void *__s2, size_t __n)
    or bcmp are correct implementations.
 
    __memcmpeq is meant to be used by compilers when memcmp return is
-   only used for its bolean value.
+   only used for its boolean value.
 
    __memcmpeq is declared only for use by compilers.  Programs should
    continue to use memcmp.  */


                 reply	other threads:[~2022-06-03 19:13 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=20220603191320.AC15C3858405@sourceware.org \
    --to=hjl@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).