From: Joseph Myers <joseph@codesourcery.com>
To: Ricardo Bittencourt <bluepenguin@gmail.com>
Cc: <libc-alpha@sourceware.org>
Subject: Re: [PATCH] string: Replace outdated comments in strlen().
Date: Mon, 21 Mar 2022 18:18:22 +0000 [thread overview]
Message-ID: <alpine.DEB.2.22.394.2203211813340.262167@digraph.polyomino.org.uk> (raw)
In-Reply-To: <20220320010442.991728-1-bluepenguin@gmail.com>
Some incidental comments (this is not a review of the patch and should not
delay it going in):
* Do I understand correctly that this is a *different* comment issue from
the one described in bug 5806 with comments in various string functions?
(Maybe the issue described in comment#10 in that bug?)
* I'd still like to see the generic string function improvements discussed
in that bug getting into glibc at some point.
--
Joseph S. Myers
joseph@codesourcery.com
next prev parent reply other threads:[~2022-03-21 18:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-20 1:04 Ricardo Bittencourt
2022-03-20 4:41 ` Noah Goldstein
2022-03-21 18:18 ` Joseph Myers [this message]
2022-03-21 18:50 ` Ricardo Bittencourt
2022-04-09 15:50 ` Ricardo Bittencourt
2022-04-09 16:46 ` Noah Goldstein
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=alpine.DEB.2.22.394.2203211813340.262167@digraph.polyomino.org.uk \
--to=joseph@codesourcery.com \
--cc=bluepenguin@gmail.com \
--cc=libc-alpha@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).