From: DJ Delorie <dj@redhat.com>
To: Paul Eggert <eggert@cs.ucla.edu>
Cc: libc-alpha@sourceware.org
Subject: Re: Fix REALLOC_ZERO_BYTES_FREES comment
Date: Mon, 12 Apr 2021 15:44:12 -0400 [thread overview]
Message-ID: <xnmtu3e19v.fsf@rhel8.vm> (raw)
In-Reply-To: <a7da171a-5796-5859-6d08-08f229840579@cs.ucla.edu> (message from Paul Eggert on Mon, 12 Apr 2021 00:48:02 -0700)
I'll add that, had this been in the *manual*, the original wording would
have been more appropriate. Otherwise, there's a missed expectation of
what calls an interposer would see.
We can be more lax with internal comments ;-)
prev parent reply other threads:[~2021-04-12 19:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-11 21:42 Paul Eggert
2021-04-12 6:05 ` Paul Zimmermann
2021-04-12 6:13 ` Florian Weimer
2021-04-12 6:19 ` Paul Zimmermann
2021-04-12 7:48 ` Paul Eggert
2021-04-12 7:53 ` Florian Weimer
2021-04-12 19:44 ` DJ Delorie [this message]
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=xnmtu3e19v.fsf@rhel8.vm \
--to=dj@redhat.com \
--cc=eggert@cs.ucla.edu \
--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).