public inbox for glibc-cvs@sourceware.org
help / color / mirror / Atom feed
From: Florian Weimer <fw@sourceware.org>
To: glibc-cvs@sourceware.org
Subject: [glibc] manual: Fix typo
Date: Wed, 18 Jan 2023 18:28:51 +0000 (GMT)	[thread overview]
Message-ID: <20230118182851.1ED6B3858D28@sourceware.org> (raw)

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

commit 8394b8c4617c925d7a7fab567401f07549d07b13
Author: Martin Joerg <martin.joerg@gmail.com>
Date:   Wed Jan 18 18:34:08 2023 +0100

    manual: Fix typo
    
    Reviewed-by: Philippe Mathieu-Daudé <philmd@linaro.org>

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

diff --git a/manual/string.texi b/manual/string.texi
index 0b60b3fbb4..7578aa1c26 100644
--- a/manual/string.texi
+++ b/manual/string.texi
@@ -2396,7 +2396,7 @@ is better than not using it.  At present, the only way to do a more
 thorough job is to write the entire sensitive operation in assembly
 language.  We anticipate that future compilers will recognize calls to
 @code{explicit_bzero} and take appropriate steps to erase all the
-copies of the affected data, whereever they may be.
+copies of the affected data, wherever they may be.
 
 @deftypefun void explicit_bzero (void *@var{block}, size_t @var{len})
 @standards{BSD, string.h}

             reply	other threads:[~2023-01-18 18:28 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-18 18:28 Florian Weimer [this message]
  -- strict thread matches above, loose matches on Subject: below --
2020-10-05 16:35 Jonathan Wakely

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=20230118182851.1ED6B3858D28@sourceware.org \
    --to=fw@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).