From: Carlos O'Donell <carlos@redhat.com>
To: Florian Weimer <fweimer@redhat.com>,
Martin Joerg via Libc-alpha <libc-alpha@sourceware.org>
Cc: Martin Joerg <martin.joerg@gmail.com>
Subject: Re: [PATCH] manual: Fix typo
Date: Wed, 18 Jan 2023 11:10:02 -0500 [thread overview]
Message-ID: <994d3bab-733a-640e-ab8d-6ecdcb584b20@redhat.com> (raw)
In-Reply-To: <87pmbb28uk.fsf@oldenburg.str.redhat.com>
On 1/18/23 09:52, Florian Weimer wrote:
> * Martin Joerg via Libc-alpha:
>
>> ---
>> 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}
>
> Carlos, still okay to merge this?
Absolutely. Please feel free to adjust the manual as required to correct typos
and fix bugs in the manual.
--
Cheers,
Carlos.
next prev parent reply other threads:[~2023-01-18 16:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-15 18:37 Martin Joerg
2023-01-16 8:36 ` Philippe Mathieu-Daudé
2023-01-18 14:52 ` Florian Weimer
2023-01-18 16:10 ` Carlos O'Donell [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-10-05 16:34 Jonathan Wakely
2020-10-05 16:36 ` Florian Weimer
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=994d3bab-733a-640e-ab8d-6ecdcb584b20@redhat.com \
--to=carlos@redhat.com \
--cc=fweimer@redhat.com \
--cc=libc-alpha@sourceware.org \
--cc=martin.joerg@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).